UIAlertView causes NSInvalidArgumentException (incompatible signatures)

[myster-t]

I'm experiencing an intermittent bug when showing UIAlertView's through blockskit's shortcut bk_showAlertViewWithTitle:.... The crash:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Attempted to create block invocation with incompatible signatures'

If you comment out the lines 177-179 in A2BlockInvocation.m, then everything works fine. It seems to be more prevalent in older generation phones (iphone 4/4s, iphone 5...). Could this have something to do with how isSignature:compatibleWithSignature: works on 32 bit devices vs 64 bit devices?

As for whether or not the block signatures are actually incorrect... I've triple checked every single one and they're correct.

[segiddins]

What version of BlocksKit are you running?

[myster-t]

The latest through cocoapods. 2.2.5 I believe.

[vani2]

I have the same issue, I suspect it's not depend on 32 or 64 bit devices. I got this only in swift. The problem is in the last argument of handler block. I tried to use NSInteger or Int(!) argument with no success.

[andrebraga]

++

[andrebraga]

Quick and filthy hack to make it work, by special casing this situation and this situation alone. Not written with brevity in mind but to show the special casing step by step:

    for (NSUInteger i = 2; i < numberOfArguments; i++) {
        const char methodArgument = [methodSignature getArgumentTypeAtIndex:i][0];
        const char blockArgument = [blockSignature getArgumentTypeAtIndex:i - 1][0];
        if (methodArgument != blockArgument) {
            if (@encode(int)[0] == methodArgument && @encode(long)[0] == blockArgument) {
                return YES;
            }
            return NO;
        }
    }

[myster-t]

Thanks @zwaldowski for addressing this. I haven't moved to swift yet. Does your fix also work for obj-c?

[mpurland]

@zwaldowski I have run into this issue as well. Will the commits on next branch including the fix for #260 be available on master soon?

[zwaldowski]

Yes, absolutely. We wanted to get a few things into the next branch first.

[eikebartels]

Any news on this side? The issue still exist

[hiltonc]

Just ran into this.