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 ...
PS: I have installed the Dropbox app into my device, and I am logged into it. So the official Dropbox app takes part to the authentication flow.
Hope this helps,
Mario
Greg-DB
Dropbox Staff
Dropbox StaffThanks! This all looks correct. I also just tried copying these snippets into my own sample project here though to be sure, but I still can't reproduce the issue. (And I also have the official Dropbox iOS app installed, handling the app authorization flow.)
Also, just to confirm, you're calling DBClientsManager setupWithAppKey in didFinishLaunchingWithOptions, right?
It's unclear why this would be occurring, as these unexpected classes (NSSQLiteStatementCache, NSContentSizeLayoutConstraint, and UICTFontDescriptor) seem to be from system frameworks (such as Core Data and Foundation). The Dropbox Objective-C SDK doesn't reference these classes at all.
A few more things to try to narrow this down:
- Is this reliably reproducible for you, or does it only happen on random attempts?
- Have you tried this on multiple devices? Have you tried it in the simulator?
- Have you tried completely uninstalling and reinstalling the Dropbox SDK?
- Do you have any non-standard project settings? Does this also occur for you if you set it up in a new project?
Thank you very much, Greg.
In the following days I'll try all the things you suggested. And I'll let you know.
Thank you again,
Mario
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
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.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
