-
Notifications
You must be signed in to change notification settings - Fork 1.3k
UIAlertView bk_alertViewWithTitle:message:]: unrecognized selector sent to class #235
Comments
I'm getting something similar, any idea what it is? |
HaloZero: as you can see, it's been about 2 months and no response from the author; I gave up and removed all of his code from my app... can't afford to have stuff that doesn't work or get any support in any of my apps on the App Store. Good Luck with it... |
In defense of BlocksKit, original issue has no connection to it's implementation. This code runs perfectly on latest BlocksKit in my application:
|
Yeah, I'm getting it for ANY selector. it seems like something about the codebase I'm on + BlockKit doesn't get along. Not sure what it is though |
Like even
doesn't seem to work, throwing an unrecognized selector issue. |
BlocksKit ships as a set of categories, sometimes there is difficulty in integrating it into the project. It is not faulty in design to the best of our knowledge and effort. The We cannot claim responsibility for integration issues. I spend enough of my workday fixing Xcode issues, and they are not insurmountable. The README fully addresses manual installation, and if you are encountering that much trouble, I highly recommend CocoaPods as I always have. Thanks. |
Sorry about that zwald, it's definitely an integration issue and this Github Issue was probably not the place for that discussion. I just noticed the issue and was hoping that the other commenter had a solution/guidance. Spokane-dude seems to have entitlement issues though :/ For anyone else reading this, the issue ended up being the Pods project inside Xcode was not building the right architecture, but it wouldn't throw an error, just a warning. |
This is the error message I'm getting, along with the stack trace:
This is the code I'm trying to get to run; notice that it's from the example given on GitHub. No matter if I leave the bk_cancelBlock in or out, I get the same thing. NOTHING works under BlocksKit 2.2.2! And there are NO build errors.
The text was updated successfully, but these errors were encountered: