I'm working on a ChromeOS App that integrates with Dropbox. I can't get the OAuth2 token flow to work using chrome.identity.launchWebAuthFlow. Rolling my own version of that API to do the token flow works.
The most suspicious thing I see in the browser logs is that there is a GET to /oauth2/authorize that gets aborted. First there is a GET to ttps://www.dropbox.com/oauth2/authorize?client_id=redacted&force_reapprove=true&redirect_uri=https%3A%2F%2F..., then a GET to https://www.dropbox.com/oauth2/authorize?client_id=redacted&response_type=token&redirect_uri=https:/...that gets aborted and immediately reissued. My hypothesis is that when that request is aborted, the launchWebAuthFlow API assumes that the login process has failed and gives up.
Additional information about my use case:
* I have 2-factor authentication, using Google Authenticator, configured for my account
Any thoughts or advice would be appreciated.
Looking at the two URLs you shared, the differences appear to be: (unless something got lost in formatting when posting to the forum)
Can you try initially supplying the URL exactly as it is the second, reformatted version? I believe it's technically wrong to supply it like that since the 'redirect_uri' URL parameter isn't properly URL encoded, but it may be useful for the sake of troubleshooting to see if that helps.
Have a question? Our Dropbox Community is here to help you find an answer!
You won’t have to wait too long for a reply, but why not learn more about the Community while you’re here.
Not the right discussion for you? Find out what else our Community has to say about API Support.
Or, search our Help Center for even more.