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,
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.
Greg-DB
Dropbox Staff
Dropbox StaffThe authorizedClient should only be nil if the clients were reset, or if after a relaunch the SDK wasn't able to retrieve the token from the Keychain. There isn't anything else you need to be doing to keep the authorizedClient available. Calling authorizeFromControllerV2 when you don't have an authorizedClient and need to connect to an account is the right procedure. Seeing authorizedClient automatically revert to nil is just unexpected.
Anyway, I don't see anything you're doing wrong here that should cause this, and I can't reproduce the issue here myself. Apologies for the bother, but would you be able to share a small sample project that reproduces the issue so we can investigate here? Thanks in advance!
- Dear Greg-db,
would it be helpful if I send you a promocode for the AppStore for my app I‘m facing this issue via e-mail? - Greg-DB
That may not be helpful as we wouldn't be able to inspect or debug the code directly.
I've put together a small sample project using the code snippets you provided here, just filling in the gaps as necessary. It doesn't reproduce the issue for me. (It retains the authorizedClient and can successfully make calls even after more than four hours after authorization.) Could you try it though and see if produces the issue for you?
Dear Greg-DB,
I tested your test app on different devices and it worked as expected without any problems.
Since the code of your test app is exactly the same I use in my apps except for the Dropbox appkey, the questions is, if the problems are linked with the appkey? I originally registered the apps with a long term token, which was changed automatically meanwhile in course of your initiative of replacing these tokens.
Kind regards gcarl
- Greg-DB
There shouldn't be anything unusual about your app key in particular. To check that though, you could try replacing my app key in the sample project with yours and retesting it. Please try that and let me know how it goes.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
