You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
I am working on coralNet API a web solution for coral reef Analysis.
I am working on the process of using the CoralNet API so that you can obtain sparse labels for an image using an already trained classifier (i.e. source). where we first submit a request to CoralNet ...
ENGR_MANSOOR You'll need to enable the "files.metadata.read" scope on the "Permissions" tab of the app's page on the App Console, then click "Submit". Then, authorize the app again to get a new access token (and optional refresh token) as Здравко noted, since that change is not retroactive to existing authorizations.
Hi ENGR_MANSOOR,
All you need to change is already pointed out in the error message posted. Have you done it? If not, just do it. 😉
Take in mind that associated scopes are "cached" within your token used! You need to revoke current token and reauthorize your application (login) anew, so the change can take effect.
Hope this helps.
Thanks for your kind reply. Actually I am getting confused in app authorization permission.
What should select in permission tab to resolve the issue.
Best regard!
- Greg-DB
Dropbox Staff
ENGR_MANSOOR You'll need to enable the "files.metadata.read" scope on the "Permissions" tab of the app's page on the App Console, then click "Submit". Then, authorize the app again to get a new access token (and optional refresh token) as Здравко noted, since that change is not retroactive to existing authorizations.
Thanks a lot my problem solved successfully.
A great platform to discuss issue here!
Regard!
About Discuss Dropbox Developer & API
Make connections with other developers
