Oauth Sign In Buttons Disabled on All Versions of Android WebView

[ismdcf]

Edit 01/05/18

The sign in buttons are responsive again.

-----------------------------------------------------

I know that it is not recommended to use Oauth from a webview. But I have no option as the device that the application runs on does not have chrome or other browsers installed in it. 

Everything was working as expected until yesterday when both sign in and sign in with google was greyed out, then it started working afterwards. But today it happened again and it is consisten till now. 

Following is the onConsoleMessage()

From line 0 of https://www.dropbox.com/1/oauth2/authorize?client_id=pziv6sf5b7jhjkhm&response_type=token&redirect_uri=https://www.dropbox.com/1/oauth2/redirect_receiver
D/MyApplication: Uncaught TypeError: Object function Object() { [native code] } has no method 'assign' -- From line 1 of https://cfl.dropboxstatic.com/static/compiled/js/alameda_bundle/alameda_bundle.min-vfl56Zfb_.js

What is the fix for this, is there a work around for this problem. I have also replied to a similar post in here

[Edit by Moderator: Link removed as it was invalid and appeared to be output from an error console.]

Dropbox sign in options greyed out

[scarless]

I'm seeing the same problem with Windows desktop apps.

[Greg-DB]

@ismdcf Thanks for following up. I'm glad to hear this is working again for you. 

For reference though, per the official documentation, you should process this in the system browser, and not a web view. In addition to supporting the Google Sign In flow per Google's requirements in the future, that will offer the best compatibility with the Dropbox site in general.

@scarless I see you also posted your own thread for this, so I'll follow up there:

https://www.dropboxforum.com/t5/API-Support-Feedback/Login-Dlg-quot-Sign-In-quot-button-not-working/...

[ismdcf]

Thanks @Greg-DB for the reply 🙂 

Like I have mentioned in the post, the android device our application runs on does not have a system browser or google chrome. Thus webview is the only option I have. Once we get the token we encrypt it and store it on the shared pref so that the does'nt need to sign in again. 

[Greg-DB · Accepted solution]

@ismdcf Thanks for the information. I'll pass it along to the team. While we'll try to maintain compatibility when possible, unfortunately we can't officially promise support in the future. If you are able to update the browser engine used by the web view over time, I recommend doing so.