fix: no sound when paying via QAB

[linhvovan29546]

Explanation of Change

This PR fixes the issue where no sound plays when paying a user via QAB. It also refactors the code by moving the playSound logic from the component to the corresponding action

Fixed Issues

$ #61296
PROPOSAL: #61296 (comment)

Tests

Test 1

1. Open a DM with any user

2. Click + in the composer and pay using the Pay {userName} option

3. Verify success sound is played

4. Click FAB > Click on QAB

5. Pay the user again

   • Verify that Pay elsewhere has sound
   • Verify that Pay with Expensify has sound

Test 2

• We need to verify that all places where the sound should be triggered are working correctly. eg: add comments, add task, etc
• Verify that no errors appear in the JS console

Offline tests

Same as test above

QA Steps

Same as test above

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

REC-20250513105559.mp4

Android: mWeb Chrome

REC-20250513105902.mp4

iOS: Native

REC-20250513104813.mp4

iOS: mWeb Safari

REC-20250513104302.mp4

MacOS: Chrome / Safari

REC-20250513102912.mp4

MacOS: Desktop

REC-20250513110231.mp4

[melvin-bot]

@ahmedGaber93 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[ahmedGaber93]

@linhvovan29546 Let's move the playSound to actions files as it looks cleaner, and please do that through the entire app as possible.

[linhvovan29546]

@ahmedGaber93

Let's move the playSound to actions files as it looks cleaner

I've moved the playSound logic to the actions for paying users

and please do that through the entire app as possible.

I've checked the source — moving the playSound to actions would be a big change. It might be better to handle that in a separate PR with proper testing. Based on my search, here are the actions we could consider updating:

• updateCreateTaskAndNavigate
• requestMoney
• sendInvoice
• createDistanceRequest
• startSplitBill
• splitBill
• splitBillAndOpenReport
• trackExpense
• addActions

Let me know your thoughts.

[ahmedGaber93]

moving the playSound to actions would be a big change.

@linhvovan29546 Hmm! But they look a straight forward, just moving some codes (please correct me if missed something).

Let's handle them, and If you faced any difficulties we can discuss it here. Also, no need to record videos for all of them, the current videos are enough.

[linhvovan29546]

Hmm! But they look a straight forward,

Yes, that is straightforward. I’m only concerned about the testing.

[linhvovan29546]

I'll move all to actions

[linhvovan29546]

Let's handle them

Updated! Do you have any suggestions for QA test steps?

[ahmedGaber93]

Do you have any suggestions for QA test steps?

You can use format like "repeat steps from n1 to n2 for actionX and actionY".

Also remove those steps

1. Go to staging.new.expensify.com or open app
2. Log in with a new gmail account