We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Random 'missing_scope' errors
Hi, I have been using the Dropbox iOS SDK for a number of years, and it's worked fine, and even transitioned to the v2 API a few years ago. Lately, some of my users seem to be getting this error rep...
Thanks for the response. For the past year, I have been using this to get the 'scopes', and then passing it into the V2 authorization API:
DBScopeRequest *scopeRequest = [[DBScopeRequest alloc] initWithScopeType:DBScopeTypeUser scopes:@[@"account_info.read", @"files.metadata.write", @"files.metadata.read"] includeGrantedScopes: YES];
So I apparently didn't add the "files.content.write" or "files.content.read" scopes here (though they are added on the App Console). But it's working fine since I made this change, and only in the last month did I receive reports from some users that the 'upload' isn't working anymore. Why would it have worked initially and not now?
Greg-DB
Dropbox Staff
Dropbox StaffMigrating an app to scopes itself also doesn't change any existing access tokens, so users with pre-existing (non-scoped) authorizations would continue being able to upload files based on the previous broader authorization. In this scenario, only users that newly authorized the app with that insufficient list of scopes would start seeing that error.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
