-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SOLUTION] If you have problems with iOS 9 or you need Bitcode enabled #192
Comments
It seems that main repo is no longer maintained, so I have created a fork where updated podspec to include source code instead of pre-compiled framework which allows to debug and use any custom build settings include bitcode and easy rebuilds with latest SDKs. Please note that it was tested only with use_frameworks! in podfile So another solution to the problem is to switch to the fork that includes all the latest fixes with:
to stay up-to-date with latest changes you can use:
|
Can anyone confirm that Anton's solution works? |
In this commit I have code that runs both implementations side by side anton-matosov@514db44 |
@mmckinley8 : @anton-matosov 's forked repo workd for me in Simulator. @anton-matosov : Why couldn't create issue in your fork ? Anyways I have few suggestion can you remove the dependency on CocoLumberjack and reduce the OS target dependency to 7.0 ? |
CocoaLumberjack is part of original library, but it is just compiled into the library. This is causing conflicts if you use It in your project as well. To reduce iOS version you can simply fork my repo and modify podspec file |
@anton-matosov I tried adding below statement in my podfile:
but on pod install I am getting below error messages:
Any ideas? |
My fork requires 8.1 as I was planning to use new API, but ended up creating separate derived project instead. |
@bishalg @Daemon-Devarshi I have reverted my fork to iOS 5.1 please let me know if it works for you now. Pod version is 2.1.7
|
I am very thankful for the fixes shared by you, thanks a ton 👍 Any specific reason why the |
It was crashing in iOS 9 x64 simulators only. It seems to be an issue with obj-c runtime implementation of respondsToSelector: for this platform for situation of the swizzled class pointer |
I've just inherited a project that is going to require me to get things going on iOS10 ( maybe ) it's unclear to me how you guys were able to build the framework. @anton-matosov - I pulled your fork, but it's unclear how to get things working. I tried dropping it into the Pods directory and executing the build_framework.sh but it's complaining. any tips? thanks, |
I have another derivative from freestyle called StylingKit. Integration is a bit different, but simpler and covered here https://github.com/StylingKit/StylingKit#integrating-with-your-app |
I do not support my fork original of pixate |
Hi folks,
Like other people, i had several problems with PixateFreestyle framework when i upgraded to Xcode to 7 and Mac OS X El capitan.
After some days researching, i decided to compile my own version of PixateFreestyle framework in order to avoid this problems.
You have my version here: https://www.dropbox.com/s/9cz035h67y9x7fd/PixateFreestyle.framework.zip?dl=0
If you add this framework to your project, when you execute Simulator or create an archive with bitcode enabled all will works like a charm.
If you want to build your own PixateFreestyle framework from source code, follow this steps:
Regards.
The text was updated successfully, but these errors were encountered: