I have a date picker in my app and it was working fine up until I updated to the latest Xcode.
Now when I use it it crashes and gives this error.
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[_UIDatePickerMacCompactView _setTextColor:]: unrecognized selector sent to instance 0x11135ae50'
This is an app that is on iOS and Mac OS using catalyst.
The date picker works fine on the iOS devices but crashed like this on the Mac version.
Has anyone got any idea on what may be happening, I cannot find the UIDatePickerMacCompactView in there files anywhere.
Just by reading the error message, are you setting the text color as UIColor instead of NSColor by chance. I have little experience with Catalyst so I might be wrong but that's my 2 cents.
Related
I am testing my music application compatibility on IOS7 by running it on Xcode 5 iPhone simulator(IOS7) but it crashes on retrieving all the music items using following code.
MPMediaQuery *allSongs = [[MPMediaQuery alloc] init];
NSArray *itemsFromGenericQuery = [allSongs items]; // Here application crashes
Crash log :
[__NSCFNumber libraryCompletionHandler]: unrecognized selector sent to instance 0xdd66840
This is snapshot for the threads running at the time of crash:
I am suspecting that there is some bug in Xcode5..!
EDIT : I could run the same application using Xcode 4.6.3 on simulator/device without any issue/crash.
[__NSCFNumber libraryCompletionHandler]: unrecognized selector sent to instance 0xdd66840
This error says that an object of type NSNumber was passed the message -libraryCompletionHandler. NSNumber doesn't have a -libraryCompletionHandler method, hence the crash. Obviously, something bad is going on.
Usually this is an indication of a bad cast, or a zombie. In this case, I would suspect a zombie object.
Congratz, you may have found a defect in the iOS 7 Simulator. Woo Hoo!
I am suspecting that there is some bug in Xcode5..!
There are clearly some bugs in the developer preview versions of Xcode 5, but it sounds like it's your app that's crashing rather than Xcode or the simulator itself. That would lead one to believe that the problem is more likely to be either in your app, or possibly in the operating system.
[__NSCFNumber libraryCompletionHandler]: unrecognized selector sent to instance 0xdd66840
Bad pointers are a common cause of unrecognized selector errors, especially when they involve classes that don't seem to be involved in the code that's crashing. Turn on NSZombieEnabled and set a breakpoint on all exceptions to track down the problem.
Maybe it's the project settings
Try to add -ObjC
I am getting this Error :
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[MasterViewController setRefreshControl:]: unrecognized selector sent to instance 0x2681e0'
How to resolve this issue because in simulator my app is running but on device with the same code my app is not running.
I hope your simulator is iOS6 Simulator and the device in which you tried to run may have a lower OS version ..right?
.
From UIRefreshControl Class Reference,
Availability : Available in iOS 6.0 and later.
Refresh control is new to iOS6. So if you want to support iOS5, the best thing to do is check if the refresh control class exists (you can use NSClassFromString ), and if it doesn't exists either not use it or use an alternative.
I'm implementing ShareKit, and so far so good on iOS5.1 and 6.0, however 5.0 is giving me a bit of problems in the simulator.
Whenever I execute my actionsheet and leave the program (for example to launch Facebook in browser), my app will crash with:
-[CFXPreferencesSearchListSource tryLock]: unrecognized selector sent to instance 0x957e120
What is going on? Couldn't find any similar errors out there when searching. Thanks
It's a bug of simulator 5. After UIAlertView dismissed, press CMD+SHIFT+H, the bug occurs.
In fact, it doesn't occur in physical devices. So don't panic
i am using EkSource class from Eventkit framework for creating custum calender but , when i am running application in ios 4.3.3. i am getting following error :-
2012-04-03 14:49:36.522 TimeFix[791:707] -[EKEventStore sources]:
unrecognized selector sent to instance 0x252a00 2012-04-03
14:49:36.590 TimeFix[791:707] *
Terminating app due to uncaught
exception 'NSInvalidArgumentException', reason: '-[EKEventStore
sources]: unrecognized selector sent to instance 0x252a00'
but when i am using ios 5.0 ipod for run application, is working fine with custom calender.
so please suggest me what is the is problem with ios 4.3.3.
Your error shows that you might have used something like this
[EKEventStore sources]
Am I right? If yes,
then apple doc says
sources
Returns an unordered array of source objects.
(NSArray *)sources
Return Value An unordered array of EKSource objects.
Availability Available in iOS 5.0 and later. Declared In
EKEventStore.h
So it is available in iOS 5.0 & later.
Hey guys.
I'm having this problem for 2 days now and I really don't know what to do anymore.
When I run the iPhone 4 simulator and click a specific picker, the app crashes with the
error: 'NSRangeException', reason:
'* -[NSMutableArray objectAtIndex:]:
index 4294967295 beyond bounds [0 ..
3]'
However, it doesn't happen with iPhone 3 simulator.
I know that NSNotFound is 2147483647, the longest 32bit int and 4294967295 is the longest uint 32bit but don't know what it has to do with it. -
Plus, if I run it on another user account on my Snow Leopard 10.6.4 it works just fine without giving me that crash and also, my coworker is able to run this app on his machine without having the crash too.
What can be wrong in my user account? I tried deleting the .pbxuser file form the project and having it recreate the file but without any success.
Does anyone have any ideas about this? Or what I can do on my user account that might fix this?
Thanks.
Try deleting if from the simulator, and then cleaning and rebuilding your solution.
Also, have you tried stepping through the solution one piece at a time to see what each object's value is as you go? It looks like something is not being initialized correctly...
Try deleting the app from the simulator and recompiling. It might be user data or defaults causing the issue.