-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-12-07] [HOLD for payment 2024-12-05] Android - App crashes when launching app #53150
Comments
Triggered auto assignment to @cead22 ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
This was reproducible on the Hybrid app only (editing OP). |
Non-fatal Exception: io.invertase.firebase.crashlytics.JavaScriptError: Cannot read property 'setButtonStyle' of null 8:22 |
That is the crash, its coming from the edge to edge PR on android. It seems like that in the hybrid app, when the app switches to NewDot, the module is not ready yet and it crashes #52392 |
The app does not crash anymore |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.67-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-05. 🎊 |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.68-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-07. 🎊 |
9.0.74.8 is crashing to me all the time. what's the delivery of new minor version expected to reach android app stores? what's some workaround? |
📣 @raphaelsc! 📣
|
Hi @raphaelsc! The crash issue should be resolved in a new version and its being slowly rolled out to the customers now. Let us know if you will have the same issue even after updating. Thank you! |
Upgraded to 9.0.75.6, and the issue has been fixed. Thanks for your kind reply. |
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.67-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Not reproducible on ND app.
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
App will not crash
Actual Result:
App crashes
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6677192_1732641576881.Screen_Recording_20241127_011856.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: