Just checking to see if it is necessary to first migrate a project to the new Scopes permission system before migrating to using PKCE and short-lived tokens. I notice that the Java SDK Android example requires the permissions migration but perhaps that's because it specifically uses the new scopes.
The Dropbox API itself does not technically require that these two changes (scopes and SLT/PKCE) be done at the same time. It is possible for a non-scoped app to use SLT/PKCE, and it is possible for a scoped app to not use SLT/PKCE.
However the Android authorization flow built in to the Java SDK was updated to handle both of these changes together, so if you're using that, you will need to migrate the app to scopes first.
The Dropbox API itself does not technically require that these two changes (scopes and SLT/PKCE) be done at the same time. It is possible for a non-scoped app to use SLT/PKCE, and it is possible for a scoped app to not use SLT/PKCE.
However the Android authorization flow built in to the Java SDK was updated to handle both of these changes together, so if you're using that, you will need to migrate the app to scopes first.
