You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Implementing refresh tokens for objective-c applications
Hello there. So, according to Your reminder: "on September 30th, 2021, the Dropbox OAuth flow will no longer return new long-lived access tokens. It will instead return short-lived access tokens,...
The tokenExpirationTimestamp is a unix timestamp. Parsing it should show ~4 hours until expiration, but expiration time is subject to change and should not be hardcoded.
The SDK should be handling requesting an updated access token from a refresh token for you.
Refresh tokens don't expire; though end users can revoke the authentication.
kylea
Dropbox Staff
Dropbox StaffThe tokenExpirationTimestamp is a unix timestamp. Parsing it should show ~4 hours until expiration, but expiration time is subject to change and should not be hardcoded.
The SDK should be handling requesting an updated access token from a refresh token for you.
Refresh tokens don't expire; though end users can revoke the authentication.
Thanks for the reply!
The tokenExpirationTimestamp is a unix timestamp. Parsing it should show ~4 hours until expiration, but expiration time is subject to change and should not be hardcoded.
Thanks. Good to know. Although it wouldn't be bad if this fact was reflected in the documentation (with measure units + examples).
Refresh tokens don't expire; though end users can revoke the authentication.
Yes, sorry. I meant a short-lived access token.
The SDK should be handling requesting an updated access token from a refresh token for you.
It's of course very cool. Thanks. Just to confirm that we are on the same page: I should not call DBOAuthManager.
refreshAccessToken explicitly? If a user does not sign out by himself then the SDK will not return the error 401?
- Greg-DB
That's correct, you don't need to call refreshAccessToken yourself. As long as you set things up as instructed, the SDK will handle all of that for you.
And yes, as long as nothing specifically happens to invalidate the refresh token (such as the user unlinking the app, deleting their account, etc.) the refresh token will continue to be usable.
Thanks a lot!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
