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
Re: Tokens only valid for 4 hours from app console
Dear greg-DB,
sorry, but I have to come back to this topic again, since I couldn't solve it in the recent weeks despite all these valuable hints in this forum and the description for the Swift ...
Dear Greg-DB,
it is the latter one - I get the "nil" as response in the availability check. I understood the whole discussion that this shouldn't be the case and the refresh should happen automatically via the refresh token in the background instead. Is this correct?
Thanks for the support
Greg-DB
Dropbox Staff
Dropbox StaffThanks for clarifying. That's correct, the refresh process should be handled for you automatically as long as you've processed the authorization flow using authorizeFromControllerV2.
Even if you did only have a short-lived access token stored though, or if the refresh process failed and the SDK wasn't able to get a new short-lived access token, you would still have the expired access token stored so you would have a non-nil authorizedClient and should get back a specific error like 'expired_access_token' when attempting a call.
So, from your description, with the issue occurring sooner than four hours, and with authorizedClient itself being nil, it sounds like the issue isn't actually with the access token expiration itself. It seems as if the token isn't being persisted successfully. The SDK uses the system's keychain functionality to store and retrieve the tokens.
Does the authorizedClient seem to get lost after any particular event, such as when the app (or device) is restarted?
Does this happen on multiple different devices? (I've occasionally heard of issues with the keychain not working properly on specific devices.)
Do you perhaps get any error/output during the authorizeFromControllerV2/handleRedirectURL flow?
Dear Greg-DB,
I don't get any error messages when initially connecting or reconnecting to the Dropbox. Nor is there a pattern when the reconnection doesn't work. It even happens during working with the app for a longer time when the user wants to store data on Dropbox. It happens on different devices e.g. iPhone 8 and iPhone 12.
Is there a command in swift to to initiate the refresh of the token programmatically?
- Greg-DB
There is a refreshAccessToken method, but you don't need to call that. (That's used internally, or if you want to switch to a smaller subset of scopes.) The SDK automatically performs the normal refresh process for you.
It doesn't sound like that's the issue anyway though, as the local client wouldn't get set to nil if the access token expires. The server would just return an error when an expired access token is used. Also, it doesn't seem like expiration is the issue since you're seeing this occur sooner than four hours after authorization.
Are you calling anything like unlinkClients, resetClients, or clearStoredAccessToken(s)?
Dear greg-DB,
thanks for your quick replies - highly appreciated.
No, I'm not using unlinkClients, resetClients, or clearStoredAccessToken(s) or something like it. As quoted above, I only do the setup with the DropboxClientsManager.setupWithAppKey() in appDelegate und authorize with the DropboxClientsManager.authorizeFromControllerV2(). After it I only do read and write tasks - all checked with
if let client = DropboxClientsManager.authorizedClient {... }where sometimes the nil-value is returned, in which cases then the reconnection is initiated.
In which cases turns the DropboxClientsManager.authorizedClient to nil? Do I have to handle it differently, when it is nil? Currently I'm calling the DropboxClientsManager.authorizeFromControllerV2() in these cases.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
