Using the device browser for OAuth requests instead of an embedded web-view can improve the usability of your apps significantly: users only need to sign-in to Google once per device, improving conversion rates of sign-in and authorization flows in your app.
The cleanest solution would be the device's browser for the authentication.
Answers
please have a look here:
https://stackoverflow.com/questions/40591090/403-error-thats-an-error-error-disallowed-useragent
Regards,
Google in fact no longer wants developers to use the webview:
https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html
Using the device browser for OAuth requests instead of an embedded web-view can improve the usability of your
apps significantly: users only need to sign-in to Google once per device, improving conversion rates of
sign-in and authorization flows in your app.
The cleanest solution would be the device's browser for the authentication.
Would that be a solution?
https://www.oauth.com/oauth2-servers/redirect-uris/redirect-uris-native-apps/
This will help you using the correct callback_uri during your OneAll implementation.