Need to see if your shared folder is taking up space on your dropbox 👨‍💻? Find out how to check here.

Forum Discussion

Garnik G.'s avatar
Garnik G.
Explorer | Level 4
5 years ago

DropBox API auth error - {".tag" = "expired_access_token"}

Language Swift

iOS Version 14.4

 

We have app where we use dropbox api to allow our users to upload a document.

 

This app used to working perfectly two years ago.

 

Very recently we made some small changes and trying to publish now.

 

DropBox API returns the following annoying error.

 

API Auth error - {".tag" = "expired_access_token";}

 

Please explain why in this version I am having this issue.

 

14 Replies

Replies have been turned off for this discussion
  • Greg-DB's avatar
    Greg-DB
    Icon for Dropbox Community Moderator rankDropbox Community Moderator
    5 years ago

    Even if you've uninstalled the app, the client may still be saved locally since that's persisted in the iOS keychain. And if you've disconnected the app via the Dropbox web site, the SDK won't yet know that the connection has been revoked on the server until you attempt an actual API call, like listFolder, at which point you'll get an authorization error.

     

    You can just call authorizeFromControllerV2 again to prompt the user to re-authorize the app. Or, if you do want to explicitly remove the local client, you can call unlinkClients at any time.

  • Garnik G.'s avatar
    Garnik G.
    Explorer | Level 4
    5 years ago

    That is not a solution.

     

    I can't write temporary code. I need to have normal way to verify if dbClient is valid object or not.

     

    What if user want to connect another account.

     

    There must be better approach.

     

     

  • Greg-DB's avatar
    Greg-DB
    Icon for Dropbox Community Moderator rankDropbox Community Moderator
    5 years ago

    I'm not sure understand what you mean what you mean by "temporary code". The authorization flow with authorizeFromControllerV2 works effectively the same as it did with authorizeFromController, since the SDK handles the refresh flow for you. Just like with authorizeFromController, you can just process the authorization flow with authorizeFromControllerV2 and let the SDK handle the access token details for you. You would check and use authorizedClient the same way in both cases. (While authorizeFromControllerV2 uses short-lived tokens in its implementation, it works the same way for the app's code as before, since it maintains long-term access using refresh tokens automatically just like the SDK previously maintained long-term access using long-lived access tokens from authorizeFromController.)

     

    If you want to have the user switch to a different account, you can call authorizeFromControllerV2 again and it will replace the authorizedClient.

     

    I recommend following the instructions in the current documentation. If something isn't working as expected/documented, please show both the steps/code you're using, as well as the full unexpected error/output.

  • Garnik G.'s avatar
    Garnik G.
    Explorer | Level 4
    5 years ago

    OK. I will try to see if it works also for other users. Thanks for help

     

     

     

About Dropbox API Support & Feedback

Node avatar for Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.

The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!