Invalid access token - across multiple Dropbox Team Spaces

Hi awb,

Access tokens expire! (~4 hours live) Did you ensure refresh token accompanying the access token and use it on Dropbox client object initialization?

Also, you should ensure when for some reason refresh token cannot work (when some of the cases you described comes up), your code asks the user to link your application anew. So the user will know what exactly predisposes this behavior (its recent activity).

Hope this gives direction.

awb First for reference, note that the post you linked to is old and now somewhat out of date. As Здравко noted, new Dropbox API access tokens do now expire, and access tokens and refresh tokens can also still be explicitly revoked. There are different errors for these cases: 'expired_access_token' indicates the token is expired, and 'invalid_access_token' indicates the token is not valid or is revoked.

Here's a slightly more extensive list of ways an access token/refresh token can be revoked:

• the user or team admin can revoke all access tokens for an app by unlinking it on any of the following Dropbox web pages:
  • the Connected apps page
  • the Security checkup page
  • the team member’s page on the Members section of the Business Admin console
  • the Team apps page on the Settings section of Business Admin console
• for user-linked apps, by the user: 
• for user-linked apps, by a team admin:
• for team-linked apps, by a team admin:
• any client with the access token can revoke the access token by calling /2/auth/token/revoke
• the GitHub-Dropbox token scanning partnership can revoke access tokens found publicly posted on GitHub
• if the app uses the "app folder" access type, the access token can effectively be disabled by deleting the app folder itself in the Dropbox account, via the Dropbox website or any client
• the app can be disabled
• the account that owns the app can be disabled
• the connected account/team can be disabled

To answer your specific questions:

• App folder access type: Based on your first screenshot, I can tell that your app does not use the app folder access type (because I see it has team scopes, and apps with the app folder access type can't use team scopes).
• App owner state: Based on your second screenshot, assuming it is a current screenshot, I can tell that the account that owns the app is not disabled, because only the app owner account can view that configuration page, and the account would need to be active to be able to do so.

In any case, if you are getting unexpected errors, we'll be happy to look into it, but we'd need some more information. In that case, please reply with:

• the name and version number of the platform and SDK/library you are using, if any
• the steps to reproduce the issue, including relevant code snippet(s)
• the full text of any error or unexpected output; please ideally show the full request and response, including headers and bodies for both

Be sure to redact any access tokens, refresh tokens, or app secrets throughout. Thanks!