-
Notifications
You must be signed in to change notification settings - Fork 10
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 doesn't work for Google accounts in MakeCode on some version of Android #60
Comments
Seems to be Google policy to disallow in webviews. I don't understand why it works in the iOS app. |
I can also reproduce this for me on my Android 8.1 device even though it lets me get through the whole entering password flow etc. 403: disallowed_useragent |
Reported in support ticket https://support.microbit.org/helpdesk/tickets/74336 (private) |
Reported in support ticket https://support.microbit.org/helpdesk/tickets/74736 (private) |
Reported from an iOS device via support on the 3rd of May, and in an in-person workshop on the 16th of July. |
What is the plan here? Are you using native webview in android? |
Reported in support ticket https://support.microbit.org/helpdesk/tickets/83590 |
@eanders-ms can you pitch in here? |
On the device where it's failing for MakeCode, does Google auth work for other 3rd party (non-Google) apps? |
Seems to be Google policy to disallow in webviews. This might help - I haven't read it yet! |
We may need to leverage the native Android app to manage the authentication process, which would pass the final redirect URL back to the WebView. From there we can get the auth token and cookie. Custom Tabs might be a suitable API for handling the oauth flow from the native side. |
Reported in support ticket https://support.microbit.org/helpdesk/tickets/83933 (private) |
Describe the bug
microsoft/pxt-microbit#5590
@microbit-matt-hillsdon can reproduce this.
The text was updated successfully, but these errors were encountered: