SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
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?
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
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.
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.
Please login first to submit.