Our Xamarin forms iOS app can run on an iPhone in debugger without seeing a thread crash. Its Android app doesn't have the crash issue inside or outside a debugger. Please see the crash log when running outside a debugger on an iPhone. Please help identify the cause of the thread crash. Thank you.
Incident Identifier: FE40E812-93F1-442F-BC76-4F12116F386E
CrashReporter Key: 265bac06d9728abcf4454eab4bfbc9d307da449c
Hardware Model: iPhone10,1
Process: tecommobile.iOS [382]
Path: /private/var/containers/Bundle/Application/3AC37153-DAE3-4C2C-90F3-33E4D7FD5830/tecommobile.iOS.app/tecommobile.iOS
Identifier: au.com.interlogix.tecommobilev2
Version: 152 (2.0.4)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: au.com.interlogix.tecommobilev2 [573]
Date/Time: 2021-02-22 12:52:19.6743 +1100
Launch Time: 2021-02-22 12:51:59.6754 +1100
OS Version: iPhone OS 13.5.1 (17F80)
Release Type: User
Baseband Version: 5.60.01
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 8
Thanks for your quick response.
I did include two text attachments because the max number
of characters was exceeded. You can see them as two dropdowns "Threads"
and "Binary Images" at the top of the page.
Now I have resolved the issue through removing an
additional TCP client and a timer associated with it. That was the reason that
caused the thread crash on iOS. However, it's still desirable to get your
advice on how to look at the crash log and locate the potential multithreading issue.
I know you really are an expert in the area.
I did include two text attachments because the max number
of characters was exceeded. You can see them as two dropdowns "Threads"
and "Binary Images" at the top of the page.
Now I have resolved the issue through removing an
additional TCP client and a timer associated with it. That was the reason that
caused the thread crash on iOS. However, it's still desirable to get your
advice on how to look at the crash log and locate the potential multithreading issue.
I know you really are an expert in the area.