-
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 #51707] Logged out on HybridApp after not using the app for ~12 hours #50358
Comments
Triggered auto assignment to @sakluger ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
I commented in the original thread - @trjExpensify is working on reproducing at the moment. |
No update |
We're still working on reproducing this consistently in the thread. |
@sakluger Whoops! This issue is 2 days overdue. Let's get this updated quick! |
We're still discussing in the Slack thread. |
@sakluger this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@sakluger Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not really sure what the next step is here so I asked in the Slack thread: https://expensify.slack.com/archives/C049HHMV9SM/p1728142235488769 |
This behavior is expected for unvalidated accounts - unvalidated accounts are logged out after 2+ hours of inactivity because we don’t give them an infinite session. I updated the OP steps the focus on existing accounts instead of unvalidated ones, and moved the priority to weekly. |
This is a duplicate - we'll work on it over here since it has a good #quality thread with CallStack on the go: #51185 |
Hmm, gotcha. That issue OP doesn't sound like this issue on mobile (incl. HybridApp). 🤔
The bug I'm, and others are experiencing, doesn't hang on the splash screen. I'm just straight up signed out or hit the "session expired" screen. |
That thread has been a bit of a catch-all for being logged out. But it sounds like there are a variety of flavours of this, so we can keep all of the issues open while we fix the unit test that should be catching autheticate errors that aren't dismissed when going offline |
Issue not reproducible during KI retests. (First week) |
Being worked on here too: #51707 |
@muttmuure do you know why we have two GH issues for this bug? Can we consolidate? |
Because it's not conclusive yet if that issue solves the mobile/HybridApp issues:
|
Yeah this one calls out HybridApp, and we also have reports of this happening on web, so let's make sure we catch all of them |
Issue not reproducible during KI retests. (Second week) |
No updates here for now. |
Issue not reproducible during KI retests. (Third week) |
This is merged now - #52727 |
We're not seeing it anymore, I don't think, so let's close this one out. |
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.45-3
Reproducible in staging?: yes
Reproducible in production?: yes
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: @AndrewGable
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1728142235488769
Action Performed:
Expected Result:
User is not signed out
Actual Result:
“Your session has expired” message appears
Workaround:
unknown
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: