OS X 10.11 bitcode support for Dropbox Sync API?

Well at first it was because I thought it was required if you had also a WatchKit app and I didn't realize you could set that independently of the rest of the app. Plus when I first started using Xcode 7 at about the time I submitted the original post in this thread, I was receiving a ton of compile time errors because Dropbox Sync didn't support Bitcode. But I guess if it's optional then that's ok. I just didn't want Apple to reject my app update for not having it.

Definitely let us know if Apple rejects your app due to a lack of bitcode support. (If it turns out to be a requirement, we'll likely add bitcode support to the SDK.) Thanks for bearing with us through this!

Hi I am having to recompile my app for iOS 9 and am getting this error.  I didn't know you were stopping support for the Sync library.  Ugh is it hard to replace the old with the new?  I don't need any fancy capabilities just the basic functionality of what the old library provided.

+1

Bob, I'm sorry the Sync SDK deprecation caught you off guard. We wanted to give developers as much warning as possible of course, so we ran an email campaign when it was announced, but it sounds like you never saw or got it (e.g., perhaps it got filtered from your inbox). In any case, you can find the full information here: https://blogs.dropbox.com/developers/2015/04/deprecating-the-sync-and-datastore-apis/

The specifics of migrating will depend heavily on how and to what extent your app uses the Sync SDK. If you run in to any issues of course, just let us know and we'll be happy to help.

Hi Gregory,

  Ha -- now that I look at the documentation, it is not the Sync API I am using but the original API from 2010!  I figured that it would stop being supported eventually.    For years I have gotten the warning that  [[self restClient] uploadFile: toPath: fromPath:] was deprecated, but there didn't ever seem to be a simple replacement for it.

Is there anything special I should know if I am going to be updating from that old API?  

Hi Gregory,

  Ha -- now that I look at the documentation, it is not the Sync API I am using but the original API from 2010!  I figured that it would stop being supported eventually.    For years I have gotten the warning that  uploadFile: toPath: fromPath: was deprecated, but there didn't ever seem to be a simple replacement for it.

Is there anything special I should know if I am going to be updating from that old API?  

Oh, great! We haven't released an update to the iOS Core SDK with bitcode, but if you need bitcode support for the Core SDK, you can add the source directly, since it's open source. There's a thread about this for the Core SDK here:

https://www.dropboxforum.com/hc/en-us/community/posts/204352929-Need-Bitcode-Framework

Was that a sarcastic 'great'? Isn't that sort of bad that I am still on the API from 2010? 

For now I just turned Bitcode support off in my projects, my apps are super small anyway so it wouldn't make much difference.  I've submitted my update using the still-working ancient API calls.  But I guess I need to get to work on another update which incorporates the modern API. 

Sorry, no sarcasm intended. I just meant it was great that you won't have to do the work to migrate off of the Sync SDK.

To clarify though, both the Core SDK and Sync SDK are built on v1 of the Core API, which is still supported. It's just the client-side Sync SDK itself that is deprecated, so you don't have any migration work to do right now.