oAuth 2.0 has stopped working since electron (Chromium client)

[Greg-DB]

@chrisgch Thanks for the report. Unfortunately, similar to the original report on this thread, processing the OAuth app authorization flow in a web view, not the system browser itself, is not supported.

Per the Dropbox /oauth2/authorize documentation, we do not support processing the OAuth app authorization flow in web views. (This decision was made in order to support the Google Sign In flow for signing in to Dropbox. That may still work at the moment, but Google has deprecated it, so it will stop working in the future.)

That being the case, you should update your app to process the OAuth app authorization flow in the system browser instead.

[chrisgch]

I get the same hanging dialog with the Android 4.3 system browser. It does work with Chrome, but not everyone has it installed. Using AccountManager seems to require Google Play services, so it wouldn't work on devices without them, like Amazon Fire tablets.

[Greg-DB]

@chrisgch I'm afraid the Android 4.3 system browser (which seems to be based on Webkit 534.30) isn't officially supported either, given how old it is. I recommend having your users upgrade to a more recent version.

[chrisgch]

You cannot update the system browser. But I could show a warning that users should install Chrome or Firefox for Android.