So in the app that I am developing I have multi threading. There are some thread that call managedObjectContext from appeDelegate and update database and also calling the same managedObjectContext to retrive data.
Sometimes I am getting the following error on this line.
2016-04-01 19:23:41.094 Tamil League[878:219638] -[_CDSnapshot_Matches_ values]: unrecognized selector sent to instance 0x17e5c790
2016-04-01 19:23:41.095 Tamil League[878:219638] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[_CDSnapshot_Matches_ values]: unrecognized selector sent to instance 0x17e5c790'
*** First throw call stack:
(0x245362eb 0x23d02dff 0x2453bab5 0x2453970f 0x24468c88 0x25d31985 0x25d31343 0x25c925fd 0x25c91375 0x25c5e8c1 0x25d1a4d7 0x25d22b47 0x149acab 0x14a44a3 0x25d14929 0x25c5e3b7 0x25c813ab 0xe0e70 0xdd9c4 0x24a3796d 0x24a46ef7 0x24d3a52d 0x24c9beff 0x24c8e2ef 0x24d3c7ed 0x14a55c3 0x149defb 0x14a6ab7 0x14a6909 0x2426ce0d 0x2426c9fc)
libc++abi.dylib: terminating with uncaught exception of type NSException
I tried to search on net but nothing improved my problem. Does anyone know how to solve this in swift 2.0?
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 am trying to compile my code in Xcode 9 which was perfectly working in Xcode 8.3, now it crashes on Segue from table view to uiviewcontroller.
This is the error message.
2017-10-11 10:44:36.410414-0500 Dev_TenantMoveIn[307:18597] -[PDFViewController initWithCoder:]: unrecognized selector sent to instance 0x1c80111d0
2017-10-11 10:44:36.412182-0500 Dev_TenantMoveIn[307:18597] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[PDFViewController initWithCoder:]: unrecognized selector sent to instance 0x1c80111d0'
*** First throw call stack:
(0x186a0fd38 ........ 0x1863fa56c)
libc++abi.dylib: terminating with uncaught exception of type NSException
Any suggestion would be helpful
I just updated to Parse SDK 1.9.1 and FBSDK 4.7.1. I haven't changed any code, and all of a sudden when logging into Facebook I've been getting this error:
2015-10-30 13:49:01.392 [2834:809095] -[FBSDKLoginManager logInWithReadPermissions:fromViewController:handler:]: unrecognized selector sent to instance 0x12de5d360
2015-10-30 13:49:01.404 [2834:809095] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FBSDKLoginManager logInWithReadPermissions:fromViewController:handler:]: unrecognized selector sent to instance 0x12de5d360'
*** First throw call stack:
(0x182f60f48 0x197b13f80 0x182f67c5c 0x182f64c00 0x182e68cac 0x1003d254c 0x1003d136c 0x1003d11f0 0x100241758 0x100247578 0x100247de0 0x1002ec864 0x1002f08cc 0x1002f0618 0x1002ed504 0x1002f1c68 0x1002a1868 0x10012ec5c 0x10012edcc 0x1887a2f24 0x1887a2994 0x1887aaedc 0x1887b10c0 0x1887b04c4 0x18879af14 0x18879ab9c 0x18cd7f7c4 0x18cd7fb44 0x182f18544 0x182f17fd8 0x182f15cd8 0x182e44ca0 0x18e080088 0x18855cffc 0x10013071c 0x1983628b8)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)
I'm not using logInWithReadPermissions:fromViewController as that wasn't available in the previous SDKs I had. I think Facebook just added that in, but it's not covered by the Parse SDKs. I'm using class func logInInBackgroundWithReadPermissions(permissions: [String]?, block: PFUserResultBlock?).
So it looks like I'm missing that viewController parameter but Parse says nothing about it. What should I do? Thanks!
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.
My iOS game is crashing when using Chartboost, but this wasn't happening 2 days ago, it worked fine then and I haven't changed anything.
I am doing the following:
[Chartboost startWithAppId:#"<<AppID>>" appSignature:#"<<Signature>>" delegate:self];
[[Chartboost sharedChartboost] showInterstitial:CBLocationHomeScreen];
I have removed the AppID and Signature for security reasons, but in my code they are the correct values
This crashes with the error:
2014-06-13 10:09:53.655 3D Line[7903:890b] -[__NSArrayI objectForKey:]: unrecognized selector sent to instance 0x17801e200
2014-06-13 10:09:53.684 3D Line[7903:890b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSArrayI objectForKey:]: unrecognized selector sent to instance 0x17801e200'
*** First throw call stack:
(0x18324af50 0x18f7541fc 0x18324fc04 0x18324d930 0x18316d5dc 0x1001dcf14 0x1001cc430 0x1001cecd0 0x1001cf0d4 0x18fd2c014 0x18fd2bfd4 0x18fd31654 0x18fd2bfd4 0x18fd332b8 0x18fd334fc 0x18fec16bc 0x18fec154c)
libc++abi.dylib: terminating with uncaught exception of type NSException
I think it is to do with the JSON sent back from Chartboost. Is this happening for anyone else?
We just released a live fix for this. You do not have to update your SDK to get the fix, it's already there :)