Android Hybrid - Search - App crashes when switching between expenses of the same report.

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.0.54-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5135640&group_by=cases:section_id&group_order=asc&group_id=296775
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the Expensify app
2. Open the search section
3. Tap on "Outstanding"
4. Open any report with several expenses on it. (At least 3 or 4)
5. Open any expense on it
6. Tap on the arrow on the top left corner
7. Open another expense
8. Repeat steps 5 to 7 a few more times
9. Verify that you are able to switch between expenses without the app closing

Expected Result:

The user should be able to switch between expenses of the same report, all the necessary times, without the app closing

Actual Result:

The app crashes when switching between expenses of the same report in "Outstanding" section in search

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6648292_1730123864600.Outstanding.mp4

logs (2).txt

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @jasperhuangg (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.

[lanitochka17]

Production:

Screenrecorder-2024-10-28-16-48-40-587.mp4

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[jasperhuangg]

At the dentist, will tackle this when I'm back

[jasperhuangg]

Building a revert that might be related

[hannojg]

@lanitochka17 for debugging this issue, are you able to reproduce the bug on your device, connect it to a computer and run adb bugreport from a terminal and share the zip file here with us?

(The crash from the logs is an ANR, and in that log file we have no info to what happened. This bugreport zip file will help us to understand what caused the crash)

[jasperhuangg]

@hannojg I'm testing right now, I'll try that out

[hannojg]

Thanks! (Btw, the pr hasn't touched any UI related stuff and nothing in regards to reports, so i am not sure how likely it is related - but lets see!)