-
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
Sign in - infinite spinner for some users with incorrect NVP structure #4058
Comments
Triggered auto assignment to @johnmlee101 ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
@kavimuru Can you re-test this? It seems like we had an issue with our backend which may have caused this |
@johnmlee101 we are still able to repro. Video |
Looks like the same issue happens on web, looking at the logs it seems to be an Auth issue: logs The error is similar to https://github.com/Expensify/Expensify/issues/170673, so I'm guessing this is related to https://github.com/Expensify/Auth/pull/5747. cc @marcaaron |
Hmm interesting. I've actually been seeing similar behavior for months locally. But the logs do make it seem like there is something we missed. |
Is this only reproducible on iOS ? |
I reproduced on web by using the credentials in #4058 (comment) |
Alright so I did some investigating and thought it might have to do with the pinned reports NVP. Here's what mine looks like atm Ignoring the fact that there's a tester's NVP Maybe there was some migration at some point? I reset tester's NVP and was able to log in. So I think there's nothing to do on the code side, but unsure how many accounts have this old NVP and will be blocked from logging in. |
Hmm interesting, I think if we can run a query to check it'd be worth it. Then if there are affected accounts we can add a migration. |
Honestly, I'm super confused how we were even able to end up with this NVP. It looks like the code that sets this was seeting a csv string before and then set an array but never object 🤷♂️ |
After investigating it looks like there are only 3 affected accounts, and it seems that they're still able to load e.cash without any issues, so closing this one out. I'll clean up the 3 affected accounts in the internal issue. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
User should be able to login
Actual Result:
User is unable to login. Infinite spinner
Issue repro after app reinstall
Workaround:
Unknown
Platform:
Where is this issue occurring?
Web
iOS ✔️
Android
Desktop App
Mobile Web
Version Number:
1.0.78.0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5152177_IMG_0959.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork
The text was updated successfully, but these errors were encountered: