Working with iOS: I got this error when trying to call startScan method of a GCKDeviceScanner instance.
Any suggestions?
2014-03-27 11:03:17.814 XXX4Cast[3542:60b] -[__NSCFTimer gck_setTolerance:]: unrecognized selector sent to instance 0x8dc8260
2014-03-27 11:03:17.818 XXX4Cast[3542:60b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFTimer gck_setTolerance:]: unrecognized selector sent to instance 0x8dc8260'
Found the answer:
Under Build Settings, add "-ObjC" to the "Other Linker Flags" section.
Related
Here is the detailed error description that I am receiving in debugger bar
*** Terminating app due to uncaught exception
'NSInvalidArgumentException', reason:
'-[_NSConcreteBlockSinkObservation superlayer]: unrecognized selector
sent to instance 0x6000005a4000'
Why this is happening and what will be the solution to it?
Update:
I tried to remove some lines of code for testing, then I found another error like below
[__NSDictionaryM superlayer]: unrecognized selector sent to instance
0x6000008e8ee0
I'm getting this error trying to run a bare project from the react-native init command, on an iOS 7.1 device.
This works on the iOS simulator, so I wonder if its an iOS compatibility issue?
The Movies example app works ok on this device.
```
2016-01-08 16:34:33.224 CouchTest[1210:60b] -[__NSConcreteURLComponents queryItems]: unrecognized selector sent to instance 0x14dacc10
2016-01-08 16:34:33.226 CouchTest[1210:60b] * Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSConcreteURLComponents queryItems]: unrecognized selector sent to instance 0x14dacc10'
* First throw call stack:
(0x2edb0f83 0x39561ccf 0x2edb4917 0x2edb3203 0x2ed02768 0x10abaf 0xb47a1 0xb1735 0xb0c8b 0x39a49833 0x39a4981f 0x39a49777 0x2ed7b8a1 0x2ed7a175 0x2ece4ebf 0x2ece4ca3 0x33bea663 0x3163114d 0x9780d 0x39a6eab7)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)
```
NSURLComponents queryItems is only available on iOS8+
That's why you are seeing the crash.
See the docs here for more info: https://developer.apple.com/library/ios/documentation/Foundation/Reference/NSURLComponents_class/index.html#//apple_ref/occ/instp/NSURLComponents/queryItems
Setting an exception breakpoint will show you which class/method is making that call. Otherwise, it sounds like react-native is calling queryItems when it shouldn't.
I've updated to Parse 1.9.1, Facebook SDK v4.x, iOS 9, Swift 2, and Xcode 7. Didn't change any code and added my .plist keys for LSApplicationQueriesSchemes and App Transport Security Settings.
Now, I can't log into Facebook using class func logInInBackgroundWithReadPermissions(permissions: [String]?, block: PFUserResultBlock?) because I get this error:
2015-10-30 15:24:22.433 [2905:830174] -[FBSDKLoginManager logInWithReadPermissions:fromViewController:handler:]: unrecognized selector sent to instance 0x15ee75d60
2015-10-30 15:24:22.437 [2905:830174] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FBSDKLoginManager logInWithReadPermissions:fromViewController:handler:]: unrecognized selector sent to instance 0x15ee75d60'
*** First throw call stack:
(0x182f60f48 0x197b13f80 0x182f67c5c 0x182f64c00 0x182e68cac 0x1003de54c 0x1003dd36c 0x1003dd1f0 0x10024d8dc 0x100253578 0x100253de0 0x1002f8864 0x1002fc8cc 0x1002fc618 0x1002f9504 0x1002fdc68 0x1002ad868 0x10013ade0 0x10013af50 0x1887a2f24 0x1887a2994 0x1887aaedc 0x1887b10c0 0x1887b04c4 0x18879af14 0x18879ab9c 0x18cd7f7c4 0x18cd7fb44 0x182f18544 0x182f17fd8 0x182f15cd8 0x182e44ca0 0x18e080088 0x18855cffc 0x10013c8a0 0x1983628b8)
libc++abi.dylib: terminating with uncaught exception of type NSException
I'm not using IBuilder so I don't have anything that's not connected in my storyboard, it looks like I'm just missing that fromViewController parameter. Facebook briefly mentions it in the changelog, but the method isn't available in the ParseFacebookUtilsV4.framework and nothing like it exists for use with Parse.
What am I missing here? Why am I getting this exception everytime I log in and how can I fix it?
Has anyone developed with the libUartLib.a library?
Because I have the following error:
-[CBCentralManager retrieveConnectedPeripherals]: unrecognized selector sent to instance 0x15e868d0
2015-10-02 17:13:29.265 DAPPER[2639:1705276] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CBCentralManager retrieveConnectedPeripherals]: unrecognized selector sent to instance 0x15e868d0'
*** First throw call stack:
(0x27a5186b 0x394bedff 0x27a57035 0x27a54c8f 0x279842b8 0x1018a3 0x27714a55 0x22cdbf 0x22cdab 0x231829 0x27a14595 0x27a12a8f 0x279651e9 0x27964fdd 0x30bc9af9 0x2bbca18d 0x1002b9 0x39be9873)
libc++abi.dylib: terminating with uncaught exception of type NSException
If you refer to the documentation you will that that method was deprecated in iOS 7 and has been removed in iOS 9. The replacement is retrieveConnectedPeripheralsSithServices so you either need an updated version of the library or to update it yourself if the author hasn't done so or to identify an alternative.
I have trouble integrating BugClipper into my project.
I followed the integration instructions mentioned on their website
But, the when I continue with my build it throws the following error -
Cannot find executable for CFBundle/CFPlugIn 0x17eaf2f0 (not loaded)
2014-07-24 12:34:15.457 BugClipper[371:60b] -[SMOCInvokerView smoc_width]: unrecognized selector sent to instance 0x17eae380
2014-07-24 12:34:15.459 BugClipper[371:60b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SMOCInvokerView smoc_width]: unrecognized selector sent to instance 0x17eae380'
*** First throw call stack:
(0x2eafce83 0x391a66c7 0x2eb007b7 0x2eaff0af 0x2ea4ddc8 0x10e8bf 0x10e60f 0x3968b0af 0x3968bcdb 0x10e5e7 0x105861 0xea8e5 0x312f1aad 0x312f14f3 0x312ebb41 0x31286a07 0x31285cfd 0x312eb321 0x3373876d 0x33738357 0x2eac7777 0x2eac7713 0x2eac5edf 0x2ea30471 0x2ea30253 0x312ea5c3 0x312e5845 0xeaae5 0x3969fab7)
libc++abi.dylib: terminating with uncaught exception of type NSException
it seems the category is not loaded, better go to Build Settings of your Target App, and search for Other Linker Flag and add one line in there, -ObjC -all_load
This should definitely solve your problem.
Cheers