Android - App crashes on launch

[IuliiaHerets]

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.88-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): Samsung Galaxy Z Fold 4 / Android 14
Issue reported by: Applause Internal Team
Device used: applausetester+100106kh@applause.expensifail.com
App Component: Other

Action Performed:

1. Launch hybrid app or ND app.
2. On hybrid app, tap Continue with Email.
3. Enter email.
4. Try log in if app does not crash.

Expected Result:

App will not crash.

Actual Result:

On hybrid app, app crashes after entering email.
If already logged in, app crashes.

On ND app, app crashes right after launching.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6719842_1737462368015!QA.txt
https://github.com/user-attachments/assets/db6c6eca-b20f-42f1-81a6-9cf28ea09926

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @isabelastisser (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]

💬 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.

[lakchote]

Should be fixed by #55513

See thread here, and discussion here

[lakchote]

Asked for CP in https://expensify.slack.com/archives/C07J32337/p1737469564781189.

[lakchote]

Asked for retest in https://expensify.slack.com/archives/C9YU7BX5M/p1737472198378819.

[lakchote]

We are good to close see https://expensify.enterprise.slack.com/archives/C9YU7BX5M/p1737478213191319?thread_ts=1737472198.378819&channel=C9YU7BX5M&message_ts=1737478213.191319