I'm using Parse local data store, I set it up like this:
[Parse enableLocalDatastore];
[Parse setApplicationId:#"MY ID "
clientKey:#"MY CLIENT KEY"];
I'm using my real client key and ID, after a few moments my app crashes and this is the log I get in the Xcode console.
*** Terminating app due to uncaught exception 'BFMultipleExceptionsException', reason: 'There were multiple exceptions.'
*** First throw call stack:
(0x1856fa59c 0x195e500e4 0x1002f5acc 0x10030ad80 0x100281030 0x1006e4e30 0x1006e4df0 0x1006f19a0 0x1006f2f18 0x1966712e4 0x196670fa8)
libc++abi.dylib: terminating with uncaught exception of type NSException
any idea on what is happening?
Related
I have downloaded the Stripe iOS SDK Example Automatic Confirmation Flow model. I have integrated Stripe successfully into my iOS app and have had to revert to this example for reference as when my user now gets to the point of checkout, once a payment intent is created, the SDK can no longer handle 3DS2.
This is the output I am getting when I use a test card that requires 3D authentication. I haven't changed any code besides the backend url and publishable key in the stripe sdk https://github.com/stripe/stripe-ios
2019-07-22 19:05:29.082023+0100 Standard Integration[7508:2891014] -[TVg isChallengeMandated]: unrecognized selector sent to instance 0x281111420
2019-07-22 19:05:29.082288+0100 Standard Integration[7508:2891014] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[TVg isChallengeMandated]: unrecognized selector sent to instance 0x281111420'
*** First throw call stack:
(0x20b9eb3a8 0x20abefd00 0x20b9039f8 0x20b9f0d54 0x20b9f2b50 0x102696aa4 0x1026800dc 0x102715dec 0x1034471fc 0x10344877c 0x103456158 0x20b97b024 0x20b975cd4 0x20b975254 0x20dbb4d8c 0x23979a850 0x10221c524 0x20b430fd8)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)
I have integrated Facebook SDK(4.15.1) in my app. For iOS9 my app works properly and doesn't crash on user login. If I run the same app on iOS8 device and try to login then app crashes saying:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* setObjectForKey: object cannot be nil (key: logging_token)'
* First throw call stack:
(0x294ad45f 0x37343c8b 0x293cac53 0x11941f 0x119909 0x1198a5 0x123bcb 0x11980b 0x119741 0x1185cf 0x115571 0x2c9fae7f 0x2c9fae21 0x2c9e5c43 0x2c9fa88d 0x2c9fa567 0x2c9f3e31 0x2c9ca759 0x2cc3e2f9 0x2c9c91a9 0x29473fbf 0x294733cf 0x29471a35 0x293bf3b1 0x293bf1c3 0x309ec201 0x2ca2943d 0x976f0 0x378cfaaf)
libc++abi.dylib: terminating with uncaught exception of type NSException
I have cross checked my info.plist and observed all everything is Configured properly.
Any one help me. I getting error:
2016-05-05 15:54:54.688 DemoApp[917:239962] * Terminating app
due to uncaught exception 'NSInvalidArgumentException', reason: 'There
doesn't seem to be a valid compiled storyboard at path
'/var/mobile/Containers/Bundle/Application/A803DBD5-0B64-4854-A8E6-5717E4C1F1EF/DemoApp.app/Base.lproj/Main.storyboardc''
* First throw call stack: (0x23bb410b 0x2335ae17 0x283d9221 0x14941d 0x1142d3 0x27d286cd 0x27d28659 0x27d1064f 0x27d27fb5 0x27ce2275
0x23b76f59 0x23b7525d 0x23b7568f 0x23ac8bf9 0x23ac89e5 0x24d14ac9
0x27d58ba1 0x14e865 0x23777873) libc++abi.dylib: terminating with
uncaught exception of type NSException
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?
I have a similar situation to Uncaught exception handler not called but his is a Mac application and mine is an iOS app. The solution was to use ExceptionHandler framework but that is not available on iOS.
I have a brand new iOS single view application and it is only a few lines of code so I won't paste my whole file.
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions: (NSDictionary *)launchOptions
{
NSSetUncaughtExceptionHandler(&handler);
#throw NSInternalInconsistencyException;
return YES;
}
void handler()
{
NSLog(#"hello world");
}
So in didFinishLaunchingWithOptions I set my custom exception handler and then force a crash. The exception handler is then meant to print hello world to the console but that does not happen. Putting break points in the handler shows that execution does not enter the method. However the exception gets printed to the console anyway (default action).
2014-07-24 08:58:25.476 Exception[430:70b] *** Terminating app due to uncaught exception of class '__NSCFConstantString'
libc++abi.dylib: terminating with uncaught exception of type __NSCFConstantString
Could there be another exception handler being set by default after my handler somewhere?
UPDATE
I decided to change how I force the crash from NSInternalInconsistencyException to [[NSArray arrayWithObject:#"object"] objectAtIndex:1];. The handler is now being called and hello world is being printed to the console.
So the question now is, why did NSINternalInconsistencyException not cause the handler to be called? The error is slightly different:
2014-07-24 10:13:51.333 Exception[1474:70b] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayI objectAtIndex:]: index 1 beyond bounds [0 .. 0]'
*** First throw call stack:
...
...
...
libc++abi.dylib: terminating with uncaught exception of type NSException