refresh_token not work when user delete app floder

[cherrys]

Hello, we have a problem using the dropbox feature. I call the /oauth2/authorize interface to authorize the user and use /oauth2/token to obtain the user's access_token and refresh_token. In this case, a folder corresponding to the app is created in the Dropbox directory, for example, folder A. Subsequent files uploaded by users are uploaded to folder A. After the access_token expires, refresh_token is used in our project to obtain a new access_token. This process is normal. However, in the following scenarios, if a user deletes the A folder created based on our app, the access_token in the app expires immediately. I use refresh_token to refresh the new access_token, but it is also in the expired state. This has led to problems with our business processes. What should we do when a user deletes an app folder?

[Здравко]

Hi @cherrys ,

The only thing you can do when refresh token expires is your application A to behave like never have been linking. In other words, start OAuth flow anew. 😉 That's it.

Hope this helps.

[Greg-DB]

@cherrys Здравко is correct; a user deleting the app's app folder is similar to them disconnecting the app, such as via the "Connected apps" page. The app should prompt them to re-authorize the app to connect to their Dropbox account if they want to continue using the integration.