You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-04-16] [$500] [CRITICAL] Infinite Spinners & "Hmm... It's Not Here" Errors for on NewDot #58384
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:@davidcardoza Slack conversation (hyperlinked to channel name): #Retain
Action Performed:
Log in to Newdot
Navigate through NewDot
Expected Result:
Pages should load normally without infinite spinners or missing content errors.
Actual Result:
Continuous loading spinners, "Hmm... it's not here" messages appearing frequently
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Infinite Spinners & "Hmm... It's Not Here" Errors for on NewDot[/-][+][CRITICAL] Infinite Spinners & "Hmm... It's Not Here" Errors for on NewDot[/+]on Mar 13, 2025
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Login and go to Settings -> Troubleshoot.
Click on Invalidate for Authentication status
Click on Destroy for Device credentials
Either restart the app or navigate to the other page
Verify that you are redirected to the sign-in page and there isn't infinite loading
Activity
melvin-bot commentedon Mar 13, 2025
Triggered auto assignment to @kadiealexander (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Mar 13, 2025
Triggered auto assignment to @tylerkaraszewski (
AutoAssignerNewDotQuality)MelvinBot commentedon Mar 13, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
m-natarajan commentedon Mar 13, 2025
Assigned this to #quality project as per this comment
[-]Infinite Spinners & "Hmm... It's Not Here" Errors for on NewDot[/-][+][CRITICAL] Infinite Spinners & "Hmm... It's Not Here" Errors for on NewDot[/+]72 remaining items
jliexpensify commentedon Apr 18, 2025
Adding myself as B0 to help with payments as Kadie is OOO for the next week.
Bump @Pujan92 for the checklist!
mvtglobally commentedon Apr 19, 2025
Issue not reproducible during KI retests. (Third week)
jliexpensify commentedon Apr 20, 2025
Bumping @Pujan92 for the checklist!
melvin-bot commentedon Apr 21, 2025
@kadiealexander Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
Pujan92 commentedon Apr 22, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/791/files#r2053972018
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Do we agree 👍 or 👎
garrettmknight commentedon Apr 22, 2025
$500 approved for @Pujan92
melvin-bot commentedon Apr 28, 2025
@Pujan92 Eep! 4 days overdue now. Issues have feelings too...
mallenexpensify commentedon Apr 28, 2025
Test case created, looks like we're good to close