When i tried to click one button it moved to next UIViewcontroller and from there i click back button and it came back to the previous UIViewcontroller ,suddently it crashed.
Following are the crash report
2013-08-19 12:02:19.849 MyApp[851:907] *** Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <CALayerArray: 0x1f1f1120> was mutated while being enumerated.' *** First throw call stack: (0x34a1d2a3 0x3c67797f 0x34a1cd85 0x36827ca3 0x36827d33 0x36827d33 0x36827d33 0x36827d33 0x36827b9b 0x36a0b585 0x368538af 0x368a3f19 0x3683aab3 0x368af8ef 0x365e4c01 0x3ca8e4b7 0x3ca8fdcb 0x349f0f3b 0x34963ebd 0x34963d49 0x384e02eb 0x36879301 0xdc439 0xdc3c0) libc++abi.dylib: terminate called throwing an exception
Related
To inherit style for all textViews in my app I did
UITextView.appearance().keyboardAppearance = .dark
The problem is when I enter the screen with textView my application quits unexpectedly, in log I see:
*** Assertion failure in void PushNextClassForSettingIMP(id, SEL)(), /BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKit/UIKit-3599.6.1/UIAppearance.m:760
* Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Please file a radar on UIKit if you see this assertion.'
* First throw call stack:
When I Navigate the specific UITableView called "InvoiceViewController" from HomeViewController by didSelectRowAtIndexPath and from "TimerViewController" by sliding Slider Action. App Crashing and the compiler, throwing following error.
2017-10-30 14:57:25.181311+0400 FixtrProvider[3667:1496216] desc: -[UIView adjustedContentInset]: unrecognized selector sent to instance 0x102d16010
2017-10-30 14:57:25.181369+0400 FixtrProvider[3667:1496216] name: NSInvalidArgumentException
2017-10-30 14:57:25.181402+0400 FixtrProvider[3667:1496216] user info: (null)
2017-10-30 14:57:25.181466+0400 FixtrProvider[3667:1496216] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView adjustedContentInset]: unrecognized selector sent to instance 0x102d16010'
*** First throw call stack:
(0x18575fd38 0x184c74528 0x18576d1f8 0x18ef27cc4 0x1857656e4 0x18564b0dc 0x18eefe628 0x18eefe3f0 0x18eefdbc0 0x18eefd8f0 0x18ec18964 0x18ecf4e48 0x18ec16e04 0x18ec16a34 0x18ec1695c 0x18eb6d000 0x18973d0b4 0x189741194 0x1896aff24 0x1896d6340 0x18eb62884 0x1857078b8 0x185705270 0x18570582c 0x1856262d8 0x1874b7f84 0x18ebd3880 0x100e6a47c 0x18514a56c)
libc++abi.dylib: terminating with uncaught exception of type NSException
Properties of the invoiceViewController
Please help me to find out the issue that caused only in iOS 11 devices.
Try to rename contentScrollView in line 28 to another name or remove outlet.
This is the exception and in my ignorance of using the tools in the IDE I have a very basic question. How do I go to the line of code that causes the issue? I have located where the issue is, but rather than NSLogging a message in the didload and didAppear events, then stepping through the code until is breaks seems like a long way to figure this out. I am assuming that the [5970:1623718] is a clue, but to what?
2017-10-04 08:22:47.798 Auto Mileage - Universal[5970:1623718] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSArrayM objectAtIndex:]: index 4 beyond bounds [0 .. 3]'
*** First throw call stack:
(0x2580f91b 0x24faae17 0x2572172b 0xd89e3 0xd9e57 0x2a0d1465 0x2a0d15a5 0x2a0c0b51 0x2a0d5d1b 0x29e7523b 0x29d86a73 0x27e1ebcd 0x27e1a375 0x27e1a209 0x27e196d1 0x27e193a5 0x29d7db79 0x257d16c9 0x257cf9cd 0x257cfdff 0x2571f229 0x2571f015 0x26d0fac9 0x29df3189 0xe9159 0x253c7873)
libc++abi.dylib: terminating with uncaught exception of type NSException
You can add an "Exception Breakpoint".
Like in the picture, select "Show the Breakpoint navigator" (the blue icon on the top of the navigator), then click on the plus icon on the bottom and click on "Add Exception Breakpoint".
I have an error message when I tap very quickly in a TextView into a TableView. It crashes and gives me the error message :
*** Assertion failure in -[_UIKBRTRecognizer notifyDelegateOfCancelledTouch:],
/BuildRoot/Library/Caches/com.apple.xbs/Sources/UIKit/UIKit-3600.5.2/Keyboard/_UIKBRTRecognizer.m:996
2017-01-14 18:17:18.558043 Formbox_Dacia_BE_Bruxelles_2017[317:15523]
*** Assertion failure in -[_UIKBRTRecognizer notifyDelegateOfCancelledTouch:], /BuildRoot/Library/
Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason: 'Can't cancel on a touch that isn't already active!'
*** First throw call stack:
(0x1e00ae07 0x1d26b077 0x1e00ace1 0x1e8de0f1 0x236fbeb3 0x236fa3f1 0x3f6d67 0x402ed9 0x3fa215 0x404de1 0x404be9 0x1d866937 0x1d86648c)
libc++abi.dylib: terminating with uncaught exception of type
NSException
Any ideas ?
EDIT: It seems that it is when I click on the keyboard selection, and I press on a keyboard touch for info.
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