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
Objective-C SDK crash
Hi,
in my project I am using the Objective-C SDK: I am updating the app to use scopes and short lived tokens. I added the SDK to the project by manually copying all the classes.
I am getting ...
Hi Greg, some updates:
- Now it works: to fix the problem I completely uninstalled the Dropbox SDK and reinstalled it with Cocoapods. Nothing else worked.
- I am calling DBClientsManager.setupWithAppKey in app delegate "applicationDidBecomeActive:", but this shouldn't be a problem.
- The crash was 100% reproducible. I tried it on multiple devices, iPhones and iPads, and it crashed every time.
Thank you very much for your help :-)
Mario
Another question: if I update the configuration of my production app to use scopes and short-lived tokens, what happens to users who never update the app? Will they be able to connect the app to Dropbox in following weeks, or they will get an error? And what will happen after September 30, 2021?
Thank you,
Mario
- Greg-DB
Dropbox Staff
Any users using old versions of your app will continue to be able to use it without issue for now. Once you switch the "Access token expiration" setting for your app on the App Console to "Short-lived", or on September 30, 2021, whichever comes first, users using old versions of your app should still be able to use it, but they'll start receiving short-lived access tokens when they process the app authorization flow, instead of long-lived access tokens. Short-lived access tokens only last for four hours, at which point further API calls will fail, and the app will receive an DBAUTHAuthError (like it would currently if the user unlinks the app from their account). Exactly how your app handles that error depends on how you've programmed it. E.g., it may prompt the user to re-authorize the app.
Hi Greg,
please tell me if I am wrong.
I have updated the code of the app to use short-lived tokens, and I will release the update on the App Store in a few days.
But I haven't updated the app on the console of my Dropbox account. If so, users who update the app can connect it to Dropbox, or I need to updated the app on the console and set the "Access token expiration" to "Short-lived"? To recap, I would release the updated app on the App Store with the code using short-lived tokens, but without setting the "Access token expiration" to "Short-lived" on the console. There is something wrong about it? Or I need to set the "Access token expiration" to "Short-lived" before releasing the app update on the App Store? Is this mandatory?
Thank you very much,
Mario
- Greg-DB
You are not required to change the "Access token expiration" setting for your app. If you do not change it, existing users on old versions of your app will continue using the old flow, and users on the updated version of the app will use the new flow. If you do not change it, nothing will change for old versions of your app until September 30th, 2021.
Ok, thank you very much Greg.
I'll leave the setting as is, and I only publish the new version of the app. This seems the best approach to me.
Thank you again,
Mario
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
