[HOLD for payment 2024-11-11] [HOLD for payment 2024-11-07] Android Hybrid - Launch - App crashes everytime it is launched.

[lanitochka17]

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

---

Version Number: 9.0.55-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the Expensify app
2. Verify the app is correctly opened and can be navigated properly

Expected Result:

The user should be able to launch the app, log in and navigate properly

Actual Result:

The Expensify app crashes everytime it is launched

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

Bug6649543_1730220888290.9.0.55-2.mp4

logs3.txt

View all open jobs on GitHub

[melvin-bot]

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

[arosiclair]

@mountiny @hannojg @kirillzyusko looks like you guys just worked on this here: #51454. Can you guys take a look?

[arosiclair]

I do not have access to the beta version of OldApp atm so I'm having trouble reproducing.

[kirillzyusko]

@arosiclair in #51454 we had a different problem (the app was trying to use LocalForage which is available on web only).

The current crash happens because of this:

Caused by: undefined is not an object (evaluating 'Store.ReportHistory.bindCacheClearingEvents') at position 81:24 in app/expensify.js

[Beamanator]

@kirillzyusko i'm going to ping you in slack to see if you have any more ideas about that crash 🙏

[Beamanator]

Seems this should have been fixed in #51746, right?

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.55-10 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Run an extra grunt:build:shared in the build process to fix Android crash #51746

If no regressions arise, payment will be issued on 2024-11-07. 🎊

[arosiclair]

Fixed in #51746

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.56-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Run an extra grunt:build:shared in the build process to fix Android crash #51746

If no regressions arise, payment will be issued on 2024-11-11. 🎊