Search - Paid expense concurrently on mobile device is not shown as needed Review nor Paid

[vincdargento]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Issue was found while executing QA for PR #52333

Version Number: 9.0.76-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #52333
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Google Pixel 8, Android 14, Chrome
App Component: Search

Action Performed:

1. Log into the same account in two different windows/devices
2. Go to Search on both of them and have an expense that can be paid
3. [Device A and B] Throttle the network speed
4. [Device A and B] Approve/Pay the expense at the same time

Expected Result:

Verify that one device shows Paid and the other shows Review button with an RBR

Actual Result:

One device is shown paid but if the second device is a mobile device the expense is not shown as paid nor needed review

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @yuwenmemon (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[vincdargento]

@johncschuster FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[luacmartins]

I don't think this needs to be a blocker since it's an edge case. Demoting