Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
migrating from API 1 to 2 - how do I know if I have OAuth 1 tokens?
I am finally getting around to updating my OLD apps from the original Dropbox IOS API to the new one. I'm looking at the migration guide, and the first thing it says is to check my OAuth tokens to se...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorYes, the old SDK worked in a different way, with some other options to set for the session that don't apply to the new SDK.
Hey Greg,
I have everything working now. However, when I try to upload a build to iTunes, it rejects it. I get a bunch of errors like these:
ERROR ITMS-90087: "Unsupported Architectures. The executable for XXXXX.app/Frameworks/ObjectiveDropboxOfficial.framework contains unsupported architectures '[x86_64, i386]'."
ERROR ITMS-90209: "Invalid Segment Alignment. The app binary at 'XXXXX.app/Frameworks/ObjectiveDropboxOfficial.framework/ObjectiveDropboxOfficial' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version."
ERROR ITMS-90125: "The binary is invalid. The encryption info in the LC_ENCRYPTION_INFO load command is either missing or invalid, or the binary is already encrypted. This binary does not seem to have been built with Apple's linker."
WARNING ITMS-90080: "The executable 'Payload/XXXXX.app/Frameworks/ObjectiveDropboxOfficial.framework' is not a Position Independent Executable. Please ensure that your build settings are configured to create PIE executables. For more information refer to Technical Q&A QA1788 - Building a Position Independent Executable in the iOS Developer Library."
Any idea what the problem is? I used the Carthage method of installing the framework.
Thanks
Bob
- Greg-DBPlease double check that you followed each step of the installation instructions exactly:
https://github.com/dropbox/dropbox-sdk-obj-c#carthage
If you miss any of them it can cause issues like this. For example, I believe missing the "Input Files" step has caused issues like this before.
There was also a similar issue reported here:
https://github.com/dropbox/dropbox-sdk-obj-c/issues/67 Yes, I followed the instructions exactly. I tried it a couple of times. What's weird is that earlier today it worked, but now it doesn't. I think something about changing project targets might screw with the behavior.
I also, like that guy in the link, had some success by using Embedded Binaries earlier and then found it switching behaviors on me. I don't know, something seems flaky with that Carthage setup. I am trying the CocoaPods method now.
The CocoaPods method does not work for me either. I get this, for one thing:
Target 'ObjectiveDropboxOfficial' of project 'Pods' was rejected as an implicit dependency for 'ObjectiveDropboxOfficial.framework' because its architectures 'arm64' didn't contain all required architectures 'armv7 arm64'
Target 'Pods-XXXXXX' of project 'Pods' was rejected as an implicit dependency for 'Pods_XXXXXX'.framework' because its architectures 'arm64' didn't contain all required architectures 'armv7 arm64'
I don't like having to use the workspace file and having this CocoaPods thing screw with my XCode project, so I am going to restore from my TimeMachine backup and go back to trying to get the Carthage method to work.
Well, I got both of my builds to upload without iTunes complaining -- but there is definitely something weird going on. This morning I ripped out the Dropbox framework and settings, and installed it again via Carthage. My first target worked perfectly, uploaded fine. But the second target wouldn't run -- 'image not found'. I compared every setting for the two targets and they were exactly the same. I 'fixed' the second target by embeddeding the Dropbox framework as a binary -- it ran -- but it still wouldn't upload to iTunes due to those architecture errors.
Then without doing anything but updating the version number, I rebuilt both targets and they both ran, both uploaded too. I'm worried that my XCode project has something corrupted in it, because it is unpredictable, building a working version one minute and then a broken one the next, without me changing anything. Also my XCode hung when I tried to quit.
Anyway Greg thanks for all the help, sorry I bothered you with so many questions about this new API.
Bob
- Greg-DBThanks for following up. Sorry to hear about these building issues, but I'm glad you were able to get working builds. And no problem about the questions, that's what I'm here for!
(By the way, I highly recommend putting your project in version control and committing before any significant changes, as it can make undoing/recovering in cases like that much easier.)
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
