-
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-05-09] [Wave Collect][QBO] iOS - Accounting - App crashes after completing QBO setup flow #40517
Comments
Triggered auto assignment to @puneetlath ( |
Triggered auto assignment to @roryabraham ( |
👋 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:
|
pinged in slack: https://expensify.slack.com/archives/C036QM0SLJK/p1713481453601659 |
going to check crashlytics |
Yes, this is known, we have to update RN or add a patch. The WebView crashes when it gets unmounted, see https://expensify.slack.com/archives/C01GTK53T8Q/p1712890318658009?thread_ts=1712881940.330269&cid=C01GTK53T8Q |
It only happens in IOS native, it is an bug in react native |
I understand that we were going to soon update to RN 0.74, is that still on track? |
it's not really on track, no |
Then I guess we will need to upgrade to 0.73.5 or add the fix as a patch, do you have any preference? I'm very unfamiliar with fixing RN |
I think a minor RN upgrade would be much better than adding a patch. But it could be hard if the patches we've already got need to be ported over |
nice, then I'll try the Regarding this being a |
hmmm is QBO behind a beta? I get that it's a new feature but I'd think we wouldn't want to ship it if it crashes the app... |
It is, beta |
Need internal review from engineer for #41023 and then merge |
Merged! |
niice |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.69-2 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-05-09. 🎊 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:
|
Hey @aldo-expensify (or @roryabraham as you have permission to close issues in Firebase...) I believe this Firebase crash report matches the WebView crash that was reported in this issue. If the merged PR does resolve the crash can you please mark the firebase issue closed? Thanks! |
Issue is ready for payment but no BZ is assigned. @stephanieelliott you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@stephanieelliott)
|
Hey @rojiphil I extended an offer to you for this job on Upwork, can you please accept? https://www.upwork.com/nx/wm/offer/102258379 |
Accepted offer. Thanks |
All paid, thanks @rojiphil! |
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: 1.4.63-0
Reproducible in staging?: y
Reproducible in production?: No newfeature
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: Applause internal team
Slack conversation:
Action Performed:
Expected Result:
App does not crash after completing the setup flow.
Actual Result:
App crashes after completing the setup flow.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6453978_1713461681980.RPReplay_Final1713461021__1_.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: