Child Item

500 error when authorizing app

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?

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

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.

All comments

Greg-DB

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

rafaelgomesxyz

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!