I have implemented the AdWhirl to show different network Ads but while it shows the ads on my view and I tap to open the ad it crashes with the following displayed in the log
-[AdWhirlAdapterIAd helperNotifyDelegateOfFullScreenModal]: unrecognized selector sent to instance 0x9fce850 2012-12-08
19:40:27.571 ExerMemosApp[2294:1b203] * Terminating app due to
uncaught exception 'NSInvalidArgumentException', reason:
'-[AdWhirlAdapterIAd helperNotifyDelegateOfFullScreenModal]:
unrecognized selector sent to instance 0x9fce850'
I searched too much but couldn't find solution. Give me suggestion to remove this error.
Thanks in advance
Are you sure that the AdWhirlAdNetworkAdapter+Helpers.h file is included in your project? Make sure everything under AdWhirl/Internal is correctly referenced in your build settings.
you are not having helperNotifyDelegateOfFullScreenModal method in your File. Check that one because the name says, its delegate method. you might forgot to implement that method
Related
I don't have any code implemented in view controller to set the font or attributedLabel. But I'm seeing crash with below reason.
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: -[_SwiftValue pointSize]: unrecognized selector sent to instance 0x610001040ba0
There is another way of debugging issue. When app is crashed, check left panel and you will observe threads stack. In that find out Obj_exception_throw select that and use your logging area to run command po $arg1. This may give you the correct reason for crashing.
Or else, you can try using Application Unit tests for verifying all your IBOutlets and objects, loaded from NIBs.
You can select that xib and open it as source code.
Or search tho whole project to find that.
For some reason whenever I add a text field to my project and try type in it, the app crashes.
The errors I get are:
Can't find keyplane that supports type 4 for keyboard iPhone-PortraitChoco-NumberPad; using 1336863583_PortraitChoco_iPhone-Simple-Pad_Default
-[NSNull length]: unrecognized selector sent to instance 0x1018b1d80
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull length]: unrecognized selector sent to instance 0x1018b1d80'
This happens in both the simulator and on device. I have unchecked "Connect Hardware Keyboard" in the simulator settings also.
Do I have to handle each and every input?
So I saw a solution deep in a forum, and it did actually solve the issue.
For some reason the tab bar controller I was using was causing the issue. Simply deleting the controller, and then going Editor > Embed In > Tab Bar Controller and re adding the views fixed it.
I keep getting crash reports with the following crash:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSArrayI enumerateObjectsUsingBlock:]: unrecognized selector sent to instance
What could be triggering this crash? An empty array or something that is not an array at all? I am not able to reproduce the crash myself, I just can see it in crash logs.
You most likely have a memory issue, the fact that you can't regularly reproduce it also suggests a memory issue.
The error you are getting is saying, "we tried to call this method on this object you have a pointer to, unfortunately the object is not the type of object you told me it was going to be."
I can really only speculate given the information you've provided. Take a really fine tooth comb through your code and make sure you are not changing that object prior to that crash happening.
Try adding a debug check to make sure its the correct class. NSAsserts are NOT the solution, they are not even compiled into production apps but, it should help find the cause of the error.
NSAssert([myObject isKindOfClass:[NSArray class]], #"aw snap its not an array!");
Post more info and I can try to help further
I set up the Facebook login correctly (I'm able to log in using the Facebook button and retrieve the profile data). I followed The FB Developer guide to set up the SSK and the LoginButton.
The issue arise when I go back the button and I want to log off. This is what I get:
-[UILabel loginButtonDidLogout:]: unrecognized selector sent to instance xxxxxxx
***Terminationg App due to uncaught exception 'NSInvalidArgumentException', reason: '-[UILabel
loginButtonDidLogout:]: unrecognized selector sent to instance xxxxxx'
The class Is loaded in the appDelegate file with
[FBSDKLoginButton class];
in the .plist application file the -ObjC switch is set in the linker section.
Any ideas?? Thanks in advance
Found the issue! I was migrating from Facebook SDK v3.4 to v4. As I had a view already done for the previous login Button, I just recycled it and changed the class as the tutorial says. Deleting the view from the Storyboard, adding a new view and changing class to FBSDKLoginButton made everything work smoothly.
Thanks anyway rmaddy!
I'm getting a strange exception in Xcode 4.2.1 (ARC-enabled project) that I can't track down to the root of the problem.
This is what the exception looks like:
2012-03-18 22:19:32.855 Project[14225:707] +[UIPickerTableViewTitledCell isEqualToString:]: unrecognized selector sent to class 0x3f2bbec4
2012-03-18 22:19:32.859 Project[14225:707] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[UIPickerTableViewTitledCell isEqualToString:]: unrecognized selector sent to class 0x3f2bbec4'
What is a UIPickerTableViewTitledCell? I suppose it is some internal class for the UIPickerView to use. But I'm not referencing that class anywhere in my project.
My application is setup as a Tab Bar application with a navigation controller in each tab and this particular tab has a tableview and pickerview.
It sounds like you have an over-released object. I get that when in pre-ARC code, release is called one too many times. The code sounds like it is looking for an NSString to send isEqualToString: to but instead of getting the NSString which has been released already, it gets this random instance of UIPickerTableViewTitledCell.
I would enable Zombies. In Xcode 4.2.1, you can find it in the menu item Product > Edit Scheme. Go to the Diagnostics tab. Then there is an Enable Zombie Objects checkbox. This will make your over-released object into a Zombie, so you can figure out exactly what object is causing your crash.
I would read the Apple doc Technical Note TN2239: iOS Debugging Magic for more in-depth information on this. The whole doc is great, but you can start off by reading the sections titled "Zombies!" and "More Zombies!"