-
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
App crashes when switching workspace from workspace switcher #51005
Comments
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to @MarioExpensify ( |
💬 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:
|
👀 into it. @MonilBhavsar do you have any sample account you can share so I can reproduce the issue? |
It happens on my test account - monil+2@expensifail.com |
I think this has something to do with switching between #focus and most recent mode. I was seeing the crash consistently on each click. I am now trying to get it back by -
Currently, I see "Hmm, it's not there page" but not crash |
I am now seeing infinite loaders :/ |
I tried the above steps with my own Expensify account, I could not crash nor see infinite loaders, but it got stuck in focus mode (didn't load the rest of the chats when changed the mode to most recent). I had to logout and log back in to see everything back. |
Weird. I tried a lot but could not see a crash Btw, I still see infinite loading everywhere and broken URL Screen.Recording.2024-10-17.at.6.17.10.PM.mov |
What are we doing with this issue then?
Is that being looked into somewhere else? |
I just got a Hight Traffic account following this SO, still cannot reproduce the issue in Staging (neither the crash nor the fail to load). Is there any other step we can go through before discarding this as a DeployBlocker? Just making sure I'm not forgetting any step and possibly causing some issues down the road @trjExpensify @MonilBhavsar |
Nope, just the ones in the SO: https://stackoverflowteams.com/c/expensify/questions/9980 |
Okay, thank you @trjExpensify, closing this one as specified in the SO. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Coming from https://expensify.slack.com/archives/C049HHMV9SM/p1729164622564699
Version Number: v9.0.50-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
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: @MonilBhavsar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1729164622564699
Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
App should not crash and workspace should be switched
Actual Result:
Describe what actually happened
App crashes
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: