SciChart was built without full bitcode

Answered

I’ve got error message during compilation:

 ld: bitcode bundle could not be generated because '.../Frameworks/SciChart.framework/SciChart' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build for architecture armv7

I temporary disabled bitcode for target. Will you fix it in the next build?

Version

v1.0.0.492

iOS ios bitcode

Alexander Edunov asked 8 years ago

You must login to post comments

Answers (5)

Best Answer

Update 18th Aug 2016

SciChart v1.1.1 now supports full bitcode in the distributed framework and the Github (source code) repository.

You can download SciChart v1.1.1 or later from our Downloads page.

For more info, please see What’s New in SciChart v1.1.1

Best regards,
Andrew

Andrew Burnett-Thompson answered 8 years ago

You must login to post comments

Good question!

According to Apple App Distribution Guideline, for iOS apps, bitcode is the default, but optional. If we provide a SciChart iOS Library with bitcode, all apps and frameworks in the app bundle need to include bitcode. For watchOS and tvOS apps, bitcode is required.

At the moment, SciChart iOS v1.0.0 does not include BitCode. However, it could. Were you to become a source-code customer, you could compile the framework yourself and include this option.

For us, if we are to support it, we may have to compile two versions of the SciChart iOS framework: One with BitCode and one without BitCode. I am already in discussions with the team about the impact of this on security, our delivery pipelines and also iOS Best Practices.

If you have any comments about the above, or any clarifications on why/how you are using BitCode, please comment! The more info we get the better.

Best regards,
Andrew

Andrew Burnett-Thompson answered 8 years ago

You must login to post comments

Hi Andrew.

Bitcode should be supported. I am not sure why you think you need to provide two frameworks. A single framework that has bitcode should be able to be used in an app that doesn’t have bitcode enabled. By providing a library without bitcode you are ENSURING that no one can use the framework in an app that uses the watchOS.

Brett

Brett Park answered 8 years ago

- Andrew Burnett-Thompson
- 8 years ago
Hi Brett, thanks for your feedback! We are nearing end of sprint so the team is polishing up features + bugs reported from v1.0.0 release. I will see what we can do to prioritise this. Best regards, Andrew