Terminating app due to uncaught exception 'NSGenericException', reason: '*** Collection <NSConcreteHashTable: 0x30220c780> was mutated while being enumerated.'

Attached crash reports files

Looking at your first crash report, I see this:

Last Exception Backtrace:
0 CoreFoundation  … __exceptionPreprocess + 164 (NSException.m:249)
1 libobjc.A.dylib … objc_exception_throw + 88 (objc-exception.mm:356)
2 CoreFoundation  … __NSFastEnumerationMutationHandler + 116 (NSEnumerator.m:132)
3 Foundation      … -[NSConcreteHashTable countByEnumeratingWithState:objects:count:] + 124 (NSHashTable.m:579)
4 MyIphoneApp     … cli_signalHandler + 2452
…

This suggests a serious problem in your code. Frame 4 indicates that you’re handling a signal, and frame 3 shows that your signal handler is calling Objective-C. That’s not allowed. Signal handlers are restricted to using a tiny set of system routines, as documented in the sigaction man page.

Is this signal handler part of a crash reporter? If so, my advice is that you remove it. It’s crashing, which prevents the Apple crash reporter from doing its job. I discuss this issue in detail in Implementing Your Own Crash Reporter.

If this signal handler isn’t part of a crash reporter, please reply back with more info about what it’s supposed to do. Signal handlers are tricky to get right, and only useful in a very limited set of circumstances.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

To answer your questions -

Is this signal handler part of a crash reporter - We don't have and crash reporters in our code.

If this signal handler isn’t part of a crash reporter? - we don't have any signal handlers in our code

We don't have any crash reporters or explicit signal handling code included in our code.

We don't really have any idea about the function represented in frame 4 cli_signal_handler where that is implemented or defined, but for sure we don't have that in our project.

Is it possible that a third party/vendor framework could have that included? if so what's the way to identify in which framework that the broken implementation has?

Is it possible that a third party/vendor framework could have that included?

Yes. I have a couple of posts that explain how to such questions:

• Using a Link Map to Track Down a Symbol’s Origin

• Determining Why a Symbol is Referenced

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"