[TIMOB-28419] iOS: Handling native stack causes app crash
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Critical |
|---|
| Status | Closed |
|---|
| Resolution | Duplicate |
|---|
| Resolution Date | 2021-06-25T01:22:15.000+0000 |
|---|
| Affected Version/s | Release 10.0.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | iOS |
|---|
| Labels | n/a |
|---|
| Reporter | Hans Knöchel |
|---|
| Assignee | Joshua Quick |
|---|
| Created | 2021-04-13T18:06:33.000+0000 |
|---|
| Updated | 2021-06-25T01:22:15.000+0000 |
|---|
Description
We added a new feature to catch uncaught exceptions and log them to our server. But this turned out to actually cause more crashes than caught. The crash log is attached to this ticket. It seems like a simple missing nil check on the stack trace processing.
Attachments
I'm pretty sure I fixed this issue with the following commit, but it's on my personal branch which was never merged. My memory is a little fuzzy, but I think it handles the case where a native exception is turned into a JS exception and is unhandled. https://github.com/jquick-axway/titanium_mobile/commit/41ae2a943316d942cd907730ad6c8403838c7ff1#diff-a7f7445c15f7cad956189cefe654bbfbce35fda276155b36efeb983524b3e9d8
[~hknoechel], I created separate ticket [TIMOB-28420] which fixes how a "native" stack trace is read as shown in above link (although above link's fix was missing a
retain). This fix also allows native stack traces to be shown via an error dialog like how it works for unhandled JS exceptions. I "think" this will resolve the issue you're talking about as well.Closing as duplicate of [TIMOB-28420], which will be resolved in Titanium 10.0.1.