In our Android app, I am having an issue where the dropbox.com authorize web page does not redirect back to our app when the user clicks the Allow button. I wrote a sample app and the OAuth2 flow works fine with that app on the same device\environment.
The first time you click the Allow button once the page displays, the page seems to refresh in Chrome. It seems like it's redirecting back to itself. The app does show up as connected to the account when I look in Settings for the user on dropbox.com. So that part of the auth flow is working - it's just not redirecting to the app.
I added the AuthActivity to the manifest...
<!-- Insert your app key after “db- ...” -->
<data android:scheme="db-xxxxxxx" />
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.BROWSABLE" />
<category android:name="android.intent.category.DEFAULT" />
And I am calling Auth.startOAuth2Authentication() here...
public void authenticateNewDropbox(Activity con) //++ Added con param
// Set bool so we know on Resume that we're logging into Dropbox
mIsDropboxLogin = true;
//Kick off auth2 flow: this launches the browser, and then back to us in OnResume() in the Activity
The app was previously doing OAuth2 with the v1 SDK and it worked fine. I've tried a new AppID as well. I don't see any relevant messages in the Android Monitor in Android Studio.
Been stuck on this for a couple days and I can't understand what I'm doing wrong. Thanks for any help.
Thanks for the report! I'm not aware of anything that should cause this, so we'll have to investigate.
It will be difficult since this doesn't reproduce in a sample app, so to begin, some additional information would be helpful:
- what version number of the SDK do you have installed?
- what Android version(s) are you seeing this with?
- have you tested this on multiple devices or emulators? Do they all display the same issue?
Just getting back into this... I will follow the other suggestions, but thought I'd report this. With Chrome Remote debugging, I see one warning when the page is first opened:
conversion.js:27 Failed to execute 'write' on 'Document': It isn't possible to write into a document from an asynchronously-loaded external script unless it is explicitly opened.
One other thing is that the url does not seem to include a "redirect" parameter. Should it?
Chrome version is 61.0.3163.98 on both the Android 7.1.1 and 6.0.1 devices.
URL is... (with "xxx" being my app id)...
I tried with Firefox and it doesn't redirect back to my app either. The only difference is that after clicking the Allow button the url in the browser shows as https://www.dropbox.com/1/connect_submit and the page is blank. In Chrome the url and page didn't change.
I will share a build. Thanks.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!