-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-08-02] App crashes when updates applied in background #44859
Comments
Triggered auto assignment to @kadiealexander ( |
Triggered auto assignment to @dangrous ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
@fabioh8010 tagging you here since you seemed to have an idea on how to fix! I'm not sure how easy it's going to be to test/reproduce this given the bug... Also copying this article you shared here which may have a solution - https://www.codemzy.com/blog/fix-chunkloaderror-react |
Heyy, yes I can start working on this next week, could you assign me?
Yeah that's true, I will try to see how we can reproduce at least something similar that would trigger the flow described in the article to auto-refresh the page. |
@dangrous, @fabioh8010, @kadiealexander Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I will work on this tomorrow probably Melvin |
Hi, I'm Eugene from Callstack - expert contributor group. I have the capacity and am going to take over the issue |
Today's update: I've implemented the solution from the article. Currently, I'm working on reproducing an error that will trigger the same behavior. FYI: Tomorrow I will be OOO |
@pasyukevich any updates here? |
Sure My updates
|
Awesome! Looking forward to seeing it when it's ready. |
adding @thesahindia for review |
@dangrous, I won't be able to review this right now. Will ask someone for help. |
@allroundexperts, will be reviewing this. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-08-02. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary
BugZero Checklist (@kadiealexander)
|
Payouts due:
Please don't forget the checklist! |
@dangrous, @fabioh8010, @pasyukevich, @allroundexperts, @kadiealexander Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@allroundexperts I think we're ready to close out the checklist on this one! |
Checklist
|
Yeah that's fair! I agree that regression test is close to impossible... Leave the tab open for a long time and hope for an update to come through? I think we can just count it as an edge case we're unlikely to hit |
Sounds good! Please request payment via Newdot. Summary here. |
$250 approved for @allroundexperts |
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:
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1720035998836439
Action Performed:
Expected Result:
App reload without any issue with latest build
Actual Result:
App crashes and Clicking the green
Refresh
button just repeats the crash.Workaround:
Refreshing the browser "fixed" it
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Added full log in comments section.
Add any screenshot/video evidence
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @kadiealexanderThe text was updated successfully, but these errors were encountered: