-
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
[$250][Reproducible Steps] User Stuck on Skeleton Screen After Automatic Sign-Out and Re-Login #52857
Comments
Triggered auto assignment to @VictoriaExpensify ( |
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Job added to Upwork: https://www.upwork.com/jobs/~021859381980108974058 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
@getusha can you attempt reproduction please? This seems like it could be a 🔥 , I'm testing now too (experienced the bug late yesterday as well). @VictoriaExpensify snagging this from ya cuz I had the bug and want to try to expedite fixing it |
hmm... just tried to repro on staging, Chrome, with [email protected] and wasn't able to. wasn't able to on production on Chrome either. |
hello, I repro it on the dev ENV. |
📣 @missbond2017! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@mallenexpensify, @getusha Eep! 4 days overdue now. Issues have feelings too... |
@mallenexpensify, @getusha Still overdue 6 days?! Let's take care of this! |
@mallenexpensify, @getusha 10 days overdue. Is anyone even seeing these? Hello? |
Was unable to reproduce. Updated the title and OP to reflect we're looking for reliable reproduction steps. Added |
@mallenexpensify @getusha this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Issue not reproducible during KI retests. (First week) |
@mallenexpensify, @getusha Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@mallenexpensify @getusha this issue is now 4 weeks old, please consider:
Thanks! |
@mallenexpensify, @getusha Eep! 4 days overdue now. Issues have feelings too... |
@mallenexpensify, @getusha Still overdue 6 days?! Let's take care of this! |
Issue not reproducible during KI retests. (Second week) |
@s77rt , I think it's just the process that immediately occurs after clicking Waiting on reliable reproduction steps, likely close in the near year if no one is able to reproduct (or posts stating it's happened again) |
@mallenexpensify, @getusha 10 days overdue. Is anyone even seeing these? Hello? |
@mallenexpensify, @getusha 12 days overdue now... This issue's end is nigh! |
Issue not reproducible during KI retests. (Third week) |
This issue has not been updated in over 14 days. @mallenexpensify, @getusha eroding to Weekly issue. |
Might be a dupe of the below. asking about here |
|
Upwork job price has been updated to $250 |
LONG discussion going on about this, still trying to get to root of problem |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Checking on next steps here |
Issue not reproducible during KI retests. (Fourth week) |
Two updates being worked on, one is linked in here |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
This is 2 months old, it doesn't seem to have happened since the report and we don't have reliable reproduction steps. I'm going to close. Aldo worked on 'loading skeleton' fix here which might help here ¯_(ツ)_/¯ Comment or reopen if you disagree |
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:
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs Reproduction
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: @coleaeason
Slack conversation (hyperlinked to channel name): ts_external_expensify_bugs
Deliverable
The deliverable is to provide reliable reproduction steps for the bug. - Follow the Propose a solution for a job process to submit the steps for review”. Inc. preconditions and additional details if they’re helpful. (ie. require x beta to be enabled, must be on a Collect plan)
Action Performed:
Expected Result:
After signing back in, the user should be redirected to the dashboard or relevant page within a few seconds, with all content loading correctly.
Actual Result:
The user is stuck on a skeleton loading screen for over 10 minutes with no content appearing.
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
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @getushaThe text was updated successfully, but these errors were encountered: