Hello,

I've been trying to build the library with the latest Xcode 5, targeting iOS 7 and the 3 new default architectures "arm7 arm7s arm64". When doing so, libffi compilation fails with a bunch of errors, in the likes of

In file included from /Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/src/debug.c:26:
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/include/ffi_common.h:77:1: error: unknown type name 'ffi_status'
ffi_status ffi_prep_cif_machdep(ffi_cif *cif);
^
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/include/ffi_common.h:77:33: error: unknown type name 'ffi_cif'
ffi_status ffi_prep_cif_machdep(ffi_cif *cif);
                                ^
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/include/ffi_common.h:78:1: error: unknown type name 'ffi_status'
ffi_status ffi_prep_cif_machdep_var(ffi_cif *cif,
^
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/include/ffi_common.h:78:37: error: unknown type name 'ffi_cif'
ffi_status ffi_prep_cif_machdep_var(ffi_cif *cif,
                                    ^
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/include/ffi_common.h:84:3: error: unknown type name 'ffi_cif'
  ffi_cif *cif;
  ^
/Users/mathieudamours/Development/storm/iOS/Uptime/Pods/libffi/ios/src/debug.c:50:20: error: unknown type name 'ffi_type'
void ffi_type_test(ffi_type *a, char *file, int line)
                   ^
6 errors generated.

When reverting to architectures "arm7 arm7s" it builds fine. Is that behavior expected?

First of all, thanks so much for BlocksKit. It's a real time saver!

Now the problem: I've started using the KVO APIs (bk_addObserverForKeyPath:task:) and I'm getting some crashes when my objects are being dealloced:

An instance 0xbbf42b0 of class MyClass was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:

I've spent some time trying to debug this. I'm fairly sure I got rid of all memory issues caused by reference cycles in blocks by doing the weakSelf/strongSelf dance. But this one is strange. The only observers on the objects in question are created by the objects themselves:

__weak id weakSelf = self;

[self bk_addObserverForKeyPath:@"property" task:^(id target) {
    MyClass* strongSelf = self;
    [strongSelf doSomething];
}];

Any ideas?

I've recently updated xcode to 5.1 and BlocksKit from 2.0.0 to 2.2.0. I want to compile only for 32bit architectures.

here it's my Podfile:

platform :ios, '6.0'
inhibit_all_warnings!
pod 'BlocksKit', '2.2.0'
pod 'SVProgressHUD'
pod 'AFNetworking', '1.3.1'
pod 'libextobjc/EXTScope', '~> 0.3'

post_install do |installer|
    installer.project.targets.each do |target|
        target.build_configurations.each do |configuration|
            target.build_settings(configuration.name)['ARCHS'] = '$(ARCHS_STANDARD_32_BIT)'
        end
    end
end

and I've set the architecture of my project to ARCHS_STANDARD_32_BIT.

since this my application start crashing with exec bad access. I've double checked and I haven't updated any other library. If I go back using '2.0.0' everything works perfectly again.

basically 70% of the time I run the application the simulator (32 bit) the application crashes after 3-4 seconds.

here is a screenshot of a crash: https://www.dropbox.com/s/955ji64hdhmdoe7/Screenshot%202014-03-15%2016.45.17.png here an other: https://www.dropbox.com/s/6c6k4mpec5xrv0c/Screenshot%202014-03-15%2016.46.57.png

I've experienced the same happening in 2 other applications (same Podfile, same situation)

I know that this is pretty generic, but which other information can I provide you?

I'm trying to avoid using CocoaPods and have the BK files directly in my Xcode project but I get build errors based on the use of brackets "<...>" in the BK internal imports. I've tried all header search paths possibilities I think ("user", "framework" and "library") both with and without "recursive". From what I read it seems that within a framework one should use quotes and the brackets are only for external frameworks. Is that correct? Any ideas?

I'm pretty concerned by the use of:

- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
    [super touchesBegan:touches withEvent:event];
    BKTouchBlock block = [self associatedValueForKey:&kViewTouchDownBlockKey];
    if (block)
        block(touches, event);
}

In the UIView (BlocksKit) category. Just making sure everyone's aware that because this is in a category, super will send the message to UIView's superclass: UIResponder, and not to the original implementation of UIView's -touchesBegan:withEvent:. This is a problem because UIView might be doing important stuff in its -touchesBegan:withEvent: that could get completely bypassed by your implementation!

I'm actually surprised clang doesn't freak out with a Category is implementing a method which will also be implemented by its primary class warning - I guess it's because it's UIResponder that implements the original method...

In order to invoke the original implementation of -touchesBegan:withEvent:, you need to use Method Swizzling which has its own huge set of problems (not the least of which is the unpredictability when used with other libraries).

I bring this up because I'm getting an unpredictable, random crash in my current application under iOS 6 in the simulator, where upon touching a UI element that results in a navigation controller push/pop, the runtime will inexplicably crash sometime shortly after in the same runloop cycle with a __sel_registerName EXC_BAD_ACCESS. I can't prove that it's definitely BlocksKit right now, but when I unlink BlocksKit, I no longer see the issue. It only happens under very specific conditions and it's very difficult to replicate reliably.

Can someone tell me if I'm way off base here?

I just upgraded to version 1.5.2s, adding ARMv7s support, but now i'm getting unrecognized selector errors being thrown when running in the simulator. Is anybody else seeing this? Nothing else in my project has changed and when I revert back to the 1.5.2 version, it works just fine again.

Any thoughts?

Thanks, James

in libffi, I get these warnings /Users/Bryan/Documents/nevermore/Pods/libffi/ios/src/arm/ffi.c:325:21: Ambiguous expansion of macro 'alloca'

but this won't happen in xocde4

I just started using BlocksKit (really, really, really, really, cool, thank you so much for your hard work, it saves me a lot of time when coding).

Using it introduces a warning to my project, namely: 'warning: (armv7) /tmp/lto.o unable to open object file' After lots of Googling and efforts on my end to figure out what's going on, I've gotten as far as determining that if I turn on link time optimization for my target, the warning goes away, but it takes extremely long for builds to occur then.

I read a post referencing the same warning on xcode-users, that suggested building the library without link time optimization. I thought I'd check to see if that would break anything on BlocksKit's end, since I'm in a bit over my head with this.

Secondly, how can I get the iOS library built from the xcodeproj you provide? I cloned the repository, pulled the libffi submodule, but whenever I build the iOS library target, I'm not seeing anything produced.

Below is the portion of the build log that generates the warning: GenerateDSYMFile /Users/jpo/Library/Developer/Xcode/DerivedData/Ambur-dujxvdthybskfsepytlscqnmqebi/Build/Products/Debug-iphoneos/Ambur.app.dSYM /Users/jpo/Library/Developer/Xcode/DerivedData/Ambur-dujxvdthybskfsepytlscqnmqebi/Build/Products/Debug-iphoneos/Ambur.app/Ambur cd "/Users/jpo/Desktop/Ambur code" setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil /Users/jpo/Library/Developer/Xcode/DerivedData/Ambur-dujxvdthybskfsepytlscqnmqebi/Build/Products/Debug-iphoneos/Ambur.app/Ambur -o /Users/jpo/Library/Developer/Xcode/DerivedData/Ambur-dujxvdthybskfsepytlscqnmqebi/Build/Products/Debug-iphoneos/Ambur.app.dSYM

Hi,

when I paste the UIActionSheet example (http://dizzytechnology.com/data/BlocksKit/Categories/UIActionSheet+BlocksKit.html) to my code it works well in the simulator, but on the device (latest iOS 5) the app freezes. This is the console output:

warning: check_safe_call: could not restore current frame

warning: Unable to restore previously selected frame.

and this is the backtrace:

(gdb) bt
#0  0x00000000 in ?? ()

Any idea?

If you use BlocksKit in your project, and you also use an MPVolumeView that is displaying a "route" button (allows you to select AirPlay destination for playing audio), tapping the route button will cause a crash.

The crash references an unrecognized selector associatedValueForKey on an internal MPVolumeView action sheet subclass. Either BlocksKit's associatedValueForKey: is conflicting with Apple's own internal implementation, or else that particular action sheet subclass declares its own addButtonWithTitle:handler: method that BocksKit is unintentionally overriding with its category.

Setting a block to the properties commented below will cause a crash.

UIActionSheet *actionSheet = [UIActionSheet bk_actionSheetWithTitle:@"Test"];

// These are fine.
[actionSheet bk_addButtonWithTitle:@"Test1" handler:^{ NSLog(@"Test1"); }];
[actionSheet bk_addButtonWithTitle:@"Test2" handler:^{ NSLog(@"Test2"); }];
[actionSheet bk_addButtonWithTitle:@"Test3" handler:^{ NSLog(@"Test3"); }];
[actionSheet bk_setCancelButtonWithTitle:@"Cancel" handler:^{ NSLog(@"Cancel"); }];
[actionSheet bk_setCancelBlock:^{ NSLog(@"Cancel Block"); }];

// Any of these will crash.
[actionSheet bk_setWillShowBlock:^(UIActionSheet *actionSheet) { NSLog(@"Will Show Block"); }];
[actionSheet bk_setDidShowBlock:^(UIActionSheet *actionSheet) { NSLog(@"Did Show Block"); }];
[actionSheet bk_setWillDismissBlock:^(UIActionSheet *actionSheet, NSInteger index) { NSLog(@"Will Dismiss Block"); }];
[actionSheet bk_setDidDismissBlock:^(UIActionSheet *actionSheet, NSInteger index) { NSLog(@"Did Dismiss Block"); }];

Here is the crash.

-[UIActionSheet bk_setWillShowBlock:]: unrecognized selector sent to instance

when use uitextview and try to limit the count of character by reset the text in textViewDidChange method ,crash happen if you type to the max count then shake to undo ,click confirm

crash come to - (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex;line 94 [realDelegate alertView:alertView clickedButtonAtIndex:buttonIndex];

error msg is [NSBigMutableString substringWithRange:]: Range {19, 6} out of bounds; string length 19 (null)

The 27 line code: BOOL rightTaps = (tap.numberOfTapsRequired == numberOfTaps); should be : BOOL rightTaps = (tap.numberOfTapsRequired < numberOfTaps); and then 29 line change to: [tap requireGestureRecognizerToFail:gesture];

BlocksKit UIEditUserWordController causes A2DynamicDelegate UITextField+BlocksKit crash Chinese Chinese Chinese Chinese Chinese Chinese

http://blog.csdn.net/Sico2Sico/article/details/54969950