App: Stuck in "Launching Expensify" screen and unable to come out of the screen
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: @ryanschaffer Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1708631036916519
Action Performed:
NOTE: There are no exact reproduction steps. The following could be the reason
- Open http://exfy.com/roadmap in web
- Will prompt to switch to the desktop app
- Somehow user gets signed out
- Close the desktop app and reopen
Expected Result:
User is able to sign in and able to use the app
Actual Result:
- When exit and reopen the app, got the loading screen for a bit and then the
Launching Expensifyscreen appears. - The hyperlink to sign back in doesn’t work. Nothing happens when clicked on it and stuck in this page
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01b6cff1077d8a87dd
- Upwork Job ID: 1762232427563544576
- Last Price Increase: 2024-02-26
About this issue
- Original URL
- State: open
- Created 4 months ago
- Comments: 15 (10 by maintainers)
Thanks @eh2077 . I’m planning to push through a proposal soon for how we manage ‘needs reproduction’ issues. I’m going to bump this to weekly for now then add it to the list as an early example to start/test on.
@mallenexpensify I think it makes sense to clear up data in local storage similar to what we do when logout from web browser. Ideally I think we should reproduce this issue to better understand it, which will make us more confident about the fix. Let me take some more time to find the reproduction steps.