nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Need Bitcode Framework

Will P.7

It is not possible to build a WatchOS 2 app without the containing application also being built entirely with Bitcode. So even though a normal iOS 9 app does not require Bitcode strictly, anything with a WatchOS 2 app does including the containing iOS 9 app.

Therefore, it is critical that all libraries and frameworks such as Dropbox release at least a preliminary build that provides Bitcode.

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Thanks Will, I'm sending this along to the team as a request for bitcode in the iOS Core SDK.

Being as the iOS Core SDK is open source though, one other option here is to add the SDK source directly to your project, instead of the framework file. The source is included with the SDK download here:

https://www.dropbox.com/developers/core/sdks/ios

There are some OS X specific files in the source though, so you'll need to remove those.

Will P.7

The available library does include source code, but the necessary build script to lipo the final framework together for all architectures including the Simulator is not included as far as I can tell, so I can't reproduce a clean build without developing a new build script. If the build script were released or a separate Bitcode library made available in the immediate future, that would be helpful. It is impossible to test apps using the Dropbox SDK right now without Bitcode for any developer supporting WatchOS 2. Thanks.

Greg-DB

You can just add the source directly to your project instead of trying to rebuild the framework.

Will P.7

Well, yes, one could do that, it would be a similar few hours to creating the necessary lipo build script. All the code/imports/project would need to be reorganized to target direct code rather than use via a framework. If the Bitcode library is not around the corner releasing in the next few days, that's what I'll have to do. Releasing even a beta version of the SDK though with Bitcode turned on seems a lot simpler than having every developer go through either creating a specialized lipo build script or directly integrating all the code. Thanks.

Nuno C.3

Do you have any ETA on the release of a bitcode-enabled CoreAPI iOS SDK?

Greg-DB

No ETA right now. I recommend adding the source directly if you need it.

David M.301

Any update on an SDK with bitcode?

Greg-DB

No update right now. The best solution if you need it is to add the source directly.

David M.301

Greg, are you planning on releasing an update before iOS 9 is released?

Greg-DB

I don't have a timeline for the next update for the iOS Core SDK but I'll send this along to the team as a request.

Will P.7

We did the integrate the source method. Note that the source is woefully out of date and not even ARC ready, so make sure to insert the special compiler flag -fno-objc-arc on each Dropbox file. Also, make sure not to include all the OSX stuff. Also, Xcode will complain about many deprecated APIs it uses. (Presumably it is these issues that is stopping Dropbox from taking the short minutes required to just release a properly rebuilt library?) Would save a lot of time for developers for Dropbox to build this using the original scripts that lipo it all together properly.

Disoreanu L.

Note: For iOS apps, bitcode is the default, but optional. If you provide bitcode, all apps and frameworks in the app bundle need to include bitcode. For watchOS apps, bitcode is required.

John A.11

Any other tips for adding source to own project? After adding

Base64Transcoder.c, I get errors in my Prefix.pch (Expected identifier on first import).

Greg-DB

John, I don't recall running into any issues like that on the occasions I've added the source code directly. Can you open an API ticket with the steps to reproduce this so we can look into it?

Fabien L.

Few months later, still no bitcode enabled FW, obsolete source files,... All this is normal ?

Greg-DB

We don't have an updated Core SDK release with bitcode enabled, but I'll send this along as feedback to the team.

Fabien L.

I just realized that a new API is available. Swift based. This is probably best option.

Greg-DB

Hi all, we have a new release of the iOS Core SDK built with bitcode:

https://www.dropbox.com/developers-v1/core/sdks/ios

Fabien L.

Great news ! Thanks for this.

Georg B.8

Would be great if you could also update it via cocoapods

Greg-DB

Hi Georg, the iOS Core SDK on CocoaPods is actually maintained by the community, so the maintainer will have to make that update. I'll send this along to the team as a request to see if we can take ownership of that though.