-
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
Hybrid iOS - App gets unresponsive after logging as WS member and dismissing explanation modal #51527
Comments
👋 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:
|
Triggered auto assignment to @NikkiWines ( |
💬 A slack conversation has been started in #expensify-open-source |
The linked testrail test looks unrelated 🤔 also the precondition kinda makes me think this is NAB if it requires running a js snippet? Would also be helpful to know exactly what the snippet was that should be run |
Raised this in QA to get more detailed steps - here |
I'm not able to reproduce this on v9.0.54-2, can we get this retested please? |
Bug is still reproducible. ScreenRecording_10-28-2024.12-49-42_1.MP4 |
Ok, also able to reproduce. Separately, while using newDot via Hybrid App, I'm unable to exit out a report using the |
Reverting #51332 seems to have resolved this! Screen.Recording.2024-10-28.at.22.57.20.mov |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
Actually none of the code from the accused PR is executed in the described flow. I assume this to have the same root cause as this ticket: (the app isn't really crashing, but also just getting unresponsive and then android at some points decides to kill the app) |
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.54.1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5134614
Issue reported by: Applause - Internal Team
Action Performed:
precondition:
Expected Result:
User is able to open any report, search, account settings and FAB
Actual Result:
The app becomes unresponsive, unable to open any chat, search, account settings and FAB until the app is reopened
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6646291_1729906161080.IMG_0637.mp4
Bug6646291_1729951315106.full.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: