-
Noticed it once so far.
```
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSArrayM onReachabilityFlagsChanged:]: unrec…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…
-
```
Breakpad on iOS handles most exceptions well, but if it's rethrown you just get
something like:
0x39336564 [libobjc.A.dylib] + 0x00003564] _cache_getImp
0x39336f87 [libobjc.A.dylib] + 0…