klm1 Helpful | Level 6

The OauthPKCE .NET example, which creates an access token and a refresh token using PKCE, saves both tokens to settings. It looks like creating the DropboxClient, the access token is not needed. Is it sufficient when using short-lived tokens with the .NET SDK to only save the refresh token?

I notice the Java SDK Android example only seems to save the "credential" (access token and refresh token) when it is initially created. Is there a recommended frequency for updating the credential in preferences or is that not necessary as long as the original refresh token is still valid?

Hello! 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. Thanks!

From the OAuth guide: "Note that for certain apps, such as command line and desktop apps, it's not possible for a web browser to redirect back to your app. In these cases, your app does not need to include a redirect_uri parameter. Dropbox will present the user with an authorization code that they will need to copy and…