You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I compile the Charts lib into a Framework with Xcode 8.3.2, and give the framework to another developer to use in his Obj-C based project, they cannot use it if they are using another Xcode version other than 8.3.2.
For example, if developer creates an Obj-C project and imports the Charts framework I compiled, and attempts to compile and link in his application using Xcode 8.2.1, he will get runtime errors when attempting to use the framework.
If the developer however compiles his project with Xcode 8.2.1, it will work fine.
There is an issue the other way around as well. For example, if I compile the Charts lib using Xcode 8.1 for example, and give to a developer to compile with his project using Xcode 8.3.2, he will get runtime errors that prevent the application from launching.
I am using Charts 3.0.2.
Is there anyway around this? If the version of Xcode being used supports Swift 3.0, then I believe there shouldn't be a problem with this workflow.
The text was updated successfully, but these errors were encountered:
Just to add, the failure appears to start from the fastBindLazySymbol call from the runtime, and happens whenever I try to do anything with a ChartView(such as set its frame or set its data).
Using the Chart lib as an Xcode project is not an option. We need to use it as a framework.
This is a problem with swift without ABI stability. If the library is compiled with another version of swift then your Xcode needs to have that version of swift. Our library is compiled with swift 3.1 so you need an Xcode that has swift 3.1 which is 8.3 only.
If I compile the Charts lib into a Framework with Xcode 8.3.2, and give the framework to another developer to use in his Obj-C based project, they cannot use it if they are using another Xcode version other than 8.3.2.
For example, if developer creates an Obj-C project and imports the Charts framework I compiled, and attempts to compile and link in his application using Xcode 8.2.1, he will get runtime errors when attempting to use the framework.
If the developer however compiles his project with Xcode 8.2.1, it will work fine.
There is an issue the other way around as well. For example, if I compile the Charts lib using Xcode 8.1 for example, and give to a developer to compile with his project using Xcode 8.3.2, he will get runtime errors that prevent the application from launching.
I am using Charts 3.0.2.
Is there anyway around this? If the version of Xcode being used supports Swift 3.0, then I believe there shouldn't be a problem with this workflow.
The text was updated successfully, but these errors were encountered: