Looks like the recently released Scoped App functionality is not yet fully flaw-free.
I was just creating a new test app, and because it is recommended to use a 'Scoped app' I chose this.
- I chose 'App Folder' as a starting point, does not really matter in this case
- Gave my app a relevant name, nothing special
This step worked out just fine. After that, it was time for setting the more advanced stuff. As I am using Laravel to connect to Dropbox, I like to use Access Tokens, and therefore I chose 'Long lived' and clicked 'Generate'. The token is generated just fine. A folder is also made in my dropbox where the app sits just fine*.
Now, here it comes. I try to connect with my Laravel app, and obviously this does not work because I need to set permissions. I got a 'Bad Request' error, so I came back to the Dropbox console and clicked 'Permissions'. Here, I set the permissions to my wish, like 'files.content.read', 'files.content.write', 'files.metadata.read' and 'files.metadata.write'. Now, we would assume that these permissions are now added and we can do at least a read. Let's try...
To my surprise we get the following error: {".tag": "missing_scope", "required_scope": "files.metadata.read"}
This is strange! Because as you can see, we have set the permissions in our app.
Now, of course, this doesn't make stop trying, so we try another approach.
I deleted the app, and I create it again. Because, maybe, the token needs to be made after I set the permissions, who knows?
So, now I create a new app, with the same initial settings as before. But now, in the App page, I first set the permissions instead of first creating the API key. So, I have set my permissions, and then go back to the App main page and click Generate to generate a key. Guess what? I get the following error: "You must be a team administrator to perform this operation."
Now, Dropbox people, I would like some help with this....
For now, I will be using the old traditional Legacy Api app functionality, but I think this issue needs to be resolved...
* Which is also strange, the app's folder DID NOT GET CREATED until I clicked the 'Generate' key and this only was in the first scenario....
