We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
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....
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.
Greg-DB
Dropbox Staff
Dropbox StaffThanks 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.
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
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.
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!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
