Unrecognized isPitched selector called

Question

In my application, I show a map with annotations, and the user can view the list of annotations in a table (in the modular controller).

I am experiencing a strange error that I can reproduce both on the device and in the simulator (iOS 7 and 8).

When in static mode, if I try to select an item in my POI table view, it does one of the following:

• changes the center of the map to a random point on the map, and not to the selected annotation.
• Crashing with the message I installed (NSZombies enabled).

- [__ NSCFString isPitched]: unrecognized selector sent to instance 0x7f24e6e0

I tried several ways to solve this error, but without success. And what puzzles me, I cannot find any information about the isPitched method. This is not in my code, nor in the Apple documentation.

Does anyone know more about MapKit and the problems of these types? Alternatively, do you know a way to deactivate a tone when a user selects a POI from the list? Perhaps this will prevent the error.

EDIT: Just discovered that the isPitched method is actually part of VectorKit ! It doesn’t really help. No VectorKit documentation ...

EDIT 2: Added stack trace.

 - [__ NSCFString isPitched]: unrecognized selector sent to instance 0x7db84870 2015-02-28 14: 25: 08.501 Cartel 2015 [2481: 178443] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '- [__ NSCFString isPitched] : unrecognized selector sent to instance 0x7db84870 '*** First throw call stack: (0 CoreFoundation 0x00afb946 __exceptionPreprocess + 182 1 libobjc.A.dylib 0x00784a97 objc_exception_throw + 44 2 CoreFoundation 0x00b035c5 - [NSObject7eject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Onject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Oject_Onject_Onject_Onject_Oject_Onject_Oject_Onject_Onject_Onject_Orject_Onject_Onject_Onject_OrOject_Onject_Onject_Oject_Oject_Onject_Orject ___forwarding___ + 1047 4 CoreFoundation 0x00a4bfae _CF_forwarding_prep_0 + May 14 VectorKit 0x02dd09c1 __86- [VKMapCameraController _animateToPosition: pitch: yaw: duration: timingCurve: completion:] _ block_invoke + 1809 6 VectorKit 0x02d88645 - [VKAnimation onTimerFired:] + 357 7 VectorKit 0x02d9895e - [VKScreenCanvas animateWithTimestamp :] + 686 8 VectorKit 0x02d9850e - [VKScreenCanvas updateWithTimestamp:] + 46 9 VectorKit 0x02d71e69 - [VKMapView onTimerFired:] + 8  September 10 libobjc.A.dylib 0x0079a771 - [NSObject performSelector: withObject:] + 70 11 VectorKit 0x0323463c - [GGLDisplayLink _displayLinkFired:] + 60 12 QuartzCore 0x041abcad _ZN2CA7Display15DisplayLinkItem8dispatchEv + 45 13 QuartzCore 0x041abb83 _ZN2CA7Display11DisplayLink14dispatch_itemsEyyy + 311 14 QuartzCore 0x041ac067 _ZN2CA7Display16TimerDisplayLink8callbackEP16__CFRunLoopTimerPv + 123 15 CoreFoundation 0x00a558d6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22 16 CoreFoundation 0x00a5525d __CFRunLoopDoTimer + 1309 17 CoreFoundation 0x00a146ba __CFRunLoopRun + 2090 18 CoreFoundation 0x00a13bcb CFRunLoopRunSpecific + 443 19 CoreFoundation 0x00a139fb CFRunLoopRunInMode + 123 20 GraphicsServices 0x03f4324f GSEventRunModal + 192 21 GraphicsServices 0x03f4308c GSEventRun + 104 22 UIKit 0x00f318b6 UIApplicationMain + 1526 23 Cartel 2015 0x0001110d main + 141 24 libdyld.dylib 0x046aaac9 start + 1 25 ???  0x00000001 0x0 + 1 

Answer 1

OK, I was able to prevent a crash with the following fix.

When the POI is selected in my list, I run the view controller delegate method, which processes the MapView from the didSelect method of the tableView controller. If you have the same problem, I assume that you understand what I mean, so far.

In this method, I asked MapView to focus on the coordinates of the POI.

Now, to solve a problem that occurred only if the user’s tracking mode was set to “stun” (after your orientation), I simply added a line to deactivate this tracking mode at the beginning of my method:

[mapView setUserTrackingMode: MKUserTrackingModeNone] ; 

This fixed random crashes. Please note that this does not lead to inconsistent behavior, because this tracking mode is automatically deactivated when the user moves the map.

So, the problem is solved for me, but if you have information about this isPitched selector and what really caused the problem, you can post it here!