synman
commented
6 years ago This issue is caused by AR.Pro 3's built in crash handler detecting that the main UI thread was hung for more than 6 seconds.
This is an odd issue to occur because most heavy lifting activities are done on their own dedicated (non UI) threads.
It would be very helpful to know what the user experienced immediately prior to this crash occurring.
There is a related feature within AR.Pro 3 crash reporting that is also important to note here. If at any time during piloting (this is during active flight) if the crash handler detects a UI hang for 2 or more seconds it will trigger a controls leveling event (short circuits any in-process control inputs) and initiate a disconnect from the drone. I do this to prevent a UI lock up from freezing the drone controls which would prove to be extremely dangerous if a control input was actually being applied when the lockup occurs.
in com.github.anrwatchdog.ANRWatchDog.run
There's a lot more information about this crash on crashlytics.com: https://fabric.io/shellware/android/apps/com.shellware.arpro3/issues/5a49d4ca8cb3c2fa63025cc1?utm_medium=service_hooks-github&utm_source=issue_impact