-
Notifications
You must be signed in to change notification settings - Fork 1.3k
NSURLConnection+BlocksKit FailureBlock error #75
Comments
Hm. How odd. I'll look into it. |
Awesome. Thanks! I've tried it with both debuggers (not that I would expect that to make a difference). Both failed. Thanks again. I'm pretty stuck without your help on this :-) |
Have you also pulled in the latest A2DynamicDelegate? That code snippet is working fine on my end. Also, could you try pulling open the stack trace as much as possible, as shown here? |
Same one here:
Fails on the Compiling with iOS 5.1 SDK, latest BlocksKit and A2DynamicDelegate (pulled right now). I can't expand the stack trace more. |
Solved right now by patching
|
Hi. I have got issue with NSURLConnection too. |
Same problem with release builds. Dynamic delegates (at least, NSUrlConnection, UIAlertView, UIActionSheet) seem to be broken in the appstore version. Is it related to compiler optimisations in 'release' config? |
This bug in A2DynamicDelegate seem to be related: pandamonia/A2DynamicDelegate#9 Upd: no, it doesn't, at least for NSUrlConnection) |
Just checking in. Is this still an issue? |
Hi there,
I've been using NSURLConnection+BlocksKit successfully for a while now. However, I just upgraded to iOS 5.1 and Xcode 4.3.2 (as well as migrated to the debugger to lldb), and I now get exceptions on the following line:
myConnection.failureBlock = ^(NSURLConnection *connection, NSError *error) {
The entire snippet is:
This fails when myConnection.failureBlock is included. If I comment it out, it runs perfect.
Any idea why this is? I just pulled the latest BlocksKit master. I'm not sure how to trap the error though. The debugger just sends me back to
main()
inmain.m
. Nor am I sure how to diagnose the issue.Any ideas?
The text was updated successfully, but these errors were encountered: