Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
Hi,
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.
First, for reference, are you using the official Dropbox API v2 JavaScript SDK?
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.
I tried using the official SDK to get the login URL. Same symptoms. When I have some time I'll see if I can try the reformatted URL.
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!