-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
OAuth error when attempting to set up new phone #533
Comments
I reinstalled every door and it works so it looks like the issue is related to moving phones. I'm leaving it open because it's a bug, but testing it is difficult because it requires an install with the data being wrong in some way that happens when you move phones. |
Snap, pixel 4a to 6a |
Add pixel 7 to the list. |
Same here - Pixel 3 to 7 |
Pixel 8 has the same issue. Reinstall of the app solved it also for me. |
Looks like this is the relevant upstream ticket: teranetsrl/oauth2_client#134 Which references the even more upstream Those issues are still unsolved, but I should read the full threads and see if anybody has a good idea on bypassing the error. |
@Zverik I came to the same conclusion, did you find any solutions to the error? |
juliansteenbakker/flutter_secure_storage#354 (comment) appears to be the most widely accepted workaround, but not clear if it helps existing data. The other workaround - deleting the specific token on exception also seems to have a bit of traction |
(clear app data should also do the trick for us in userland) |
Hopefully fixed, thanks @CloCkWeRX for pointers. Please test https://github.com/Zverik/every_door/actions/runs/8775080923 if you have access. |
Since the only way I've triggered this is with a new phone I can't test right now. |
Delete and reinstall also fixes it for Pixel 8 Pro |
Thanks, I guess I'll close it then. |
I got a new phone and need to set up OAuth again. When I try to upload and press the OAuth button I get this message
every door version 3.0 on a Google Pixel 7
The text was updated successfully, but these errors were encountered: