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
Fix of aslresponse_next and aslresponse_free deprecation crashes on iOS 7 #333
Comments
This is the correct approach in handling the different versions of the framework.
|
The same with
|
Would you lie to make a pull request? Also if you could shed some light on discussion #324 it would be great. |
This is tricky. Apple header file is wrong. It says
If we compile this on Xcode 6 beta x, we don't get both symbols compiled as weak symbols. If you build a library, which incorporates CocoaLumberjack (our case), Xcode 5 will complain. I tried to add the weak symbol by directly adding it to the
Both symbols are then correctly compiled as weak:
As weaks symbols, Xcode 5 should not complain about it and simply generate |
I think we should wait a little bit more until Xcode 6 gets closer to release. In the mean time filing a bug could be a good idea. |
Has Apple responded to the radar yet? (He asked sarcastically) |
If you compile on Xcode 6 GM or later, this is fixed. |
Nice. |
i just started getting this issue, but i'm on the normal Xcode 6 release i believe |
I ran into the same issue building for Mac. (I ended up adding helper methods to hide away the switches because at first I tried something more complicated. I kind of like it this way, though.) What about this? Does the following work in your cases?
|
#365 just got merged so this should be fixed. Could everyone try it so we can close this issue and release? pod 'CocoaLumberjack', :head |
Bad luck:
Xcode 6.1 with SDK for Mac OS 10.10, building for 10.9 |
thanks for the feedback @DivineDominion, I'll be trying to resolve this by beginning of next week. |
i fixed my 7.1 device startup crash with #376, and it MAY have fixed the issue @DivineDominion ran into. |
@DivineDominion Another try with changes from #376? |
It works fine! I'd suggest moving the macro definitions outside The part in question:
|
¡that's great to hear @DivineDominion! |
Of course! Cf. #378 |
#378 is now merged, so I will close this issue. Please let me know if there is still an issue here. |
sounds good, i'll switch back to the official fork today and let you know if i run into any issues |
The current implementation of deprecation of
aslresponse_free
andaslresponse_next
is incorrect.Code compiled with Xcode 6 (iOS 8) will crash when executed on iOS 7.
This check must be also done during runtime.
The text was updated successfully, but these errors were encountered: