cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Share your feedback on the Document Scanning Experience in the Dropbox App right here.

Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

500 error when authorizing app

500 error when authorizing app

rafaelgomesxyz
New member | Level 2
Go to solution

Hello. I had initially authorized my app to upload files to its own special folder in my account, and then I disauthorized it for testing purposes. After that, I was never able to authorize it again. Whenever I go to the corresponding "https://www.dropbox.com/oauth2/authorize" URL to authorize it and click on "Allow", I get a 500 error.

 

I noticed that when I click on "Allow" a request is made to "https://www.dropbox.com/1/oauth2/authorize_submit". Isn't that endpoint from v1?

1 Accepted Solution

Accepted Solutions

Greg-DB
Dropbox Staff
Go to solution

Upon some further investigation, I've determined this can happen if you have a deleted file at the path where the app folder for the app would be normally created (e.g., /Apps/<app folder name> if your account is set to the English locale). You can work around this issue by permanently deleting the deleted file at that path via www.dropbox.com. Once you do so, you should be able to authorize the app normally.

View solution in original post

3 Replies 3

Greg-DB
Dropbox Staff
Go to solution
Thanks for the report! We'll look into that 500 error.

Also, /1/oauth2/authorize_submit is not technically just part of API v1. It's part of the OAuth 2 flow, which is used by both API v1 and API v2. It just has the "/1/" component as a matter of how it was originally implemented.

Greg-DB
Dropbox Staff
Go to solution

Upon some further investigation, I've determined this can happen if you have a deleted file at the path where the app folder for the app would be normally created (e.g., /Apps/<app folder name> if your account is set to the English locale). You can work around this issue by permanently deleting the deleted file at that path via www.dropbox.com. Once you do so, you should be able to authorize the app normally.

rafaelgomesxyz
New member | Level 2
Go to solution

I had indeed deleted the app's special folder, but that was a long time ago, so it was no longer in the trash. I managed to solve the issue by deleting the Apps folder completely. Thanks!

Need more support?
Who's talking

Top contributors to this post

  • User avatar
    rafaelgomesxyz New member | Level 2
  • User avatar
    Greg-DB Dropbox Staff
What do Dropbox user levels mean?