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
iOS SDK (Obj-C) authorisation with dropbox app installed produces error (app needs to be updated)
Hi everybody! I'm using the iOS SDK installed with cocoapods to authorise a user in order to upload files to DB. This works, as long as the DB-App isn't installed on my device (the authorisation...
Hi Greg.
Thanks for getting back to me.
I'm using ObjectiveDropboxOfficial (7.1.1)
I attached a screenshot of the error message (it's in German, though).
The error occurs when the DB-App is supposed to send me back to my App (StoryCatcher)
Greg-DB
Dropbox Staff
Dropbox StaffThanks! I'm trying this out now, but I can't seem to reproduce that error. From what I can tell though, it's actually coming from iOS itself and not directly from the Dropbox iOS app.
Given that you mentioned it occurs when the Dropbox app would be sending you back to your app, it sounds like it would be related to the URL scheme functionality that the Dropbox app and SDK use to coordinate that. Can you check that you've implemented everything from the "Application .plist file" section of the documentation as shown there? That's the configuration that allows the SDK and app to work together for that flow.
Otherwise, can you confirm which particular version number of iOS you're seeing this with? Have you tried any other versions and if so, which and do they work or not work?
Hi Greg
Thanks for your reply.
I checked my plist file and everything's as described in the document you linked to.
I am using the latest iOS-version.
One thing: When the DB-App is not installed, the authorisation flow works perfectly.
Now I saw in the document, that there should be a way to use «Safari view controller auth» instead of «Direct auth». But the document doesn't say how I'd implement this. I'd prefer to go with that approach since it proved to work before. Any hints how to tell my app to use Safari instead of the DB-app?
[Edit]
I just saw in another thread (from 2017) that the Safari auth can't be forced. Is this still the case?
Is the name I gave my app in the DB dev-console somehow related to the app's name in XCode?
Plus: The delegate method application:openUrl:options is never called when the DB app tries to re-open my app. This just an FYI...
Hi again, Greg…
I feel a bit stupid right now.
I found out that I had the app TWICE on my device. One was buried somewhere I didn't see it.
That apparently caused all sorts of confusions for the os.
I deleted both apps, installed the newest one again - and now it's working.
Such a stupid error…
Thanks a ton for your time, though!!!
- Greg-DB
Thanks for following up. I'm glad to hear you got this sorted out.
Just for reference, to answer your questions:
The SDK still doesn't offer an option to force the browser flow, but it sounds like that's no longer needed in your case anyway since you got this working.
While the app name you register on Dropbox should match the app name you use in Xcode, etc. (to avoid confusing users), it doesn't directly affect any such functionality.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
