• Replies 4 replies
  • Subscribers 16 subscribers
  • Views 928 views
  • Users 0 members are here
Options
Related

Tips to debug Error: Unhandled Exception only occurring in production build

Robert
over 5 years ago

I get the following error when my data field fires up on activity start on the device:-

Error: Unhandled Exception
Time: 2020-05-08T11:08:03Z
Part-Number: 006-B2700-00
Firmware-Version: '7.30'
Language-Code: eng
ConnectIQ-Version: 3.1.8
Store-Id: 115c4a88-78b3-44c1-aa94-4535b767a279
Store-Version: 1
Filename: A58A1831
Appname: MultiConfig
Stack:
- pc: 0x10000225
---

This does not occur in the debugger/simulator and does not occur when I side load the data field to the device with debug information.  It only occurs with the same data field uploaded as a beta and then downloaded to the device via ConnectIQ.

Is it possible to get debug information for apps downloaded from ConnectIQ?

Any tips and tricks to hunt this down gratefully appreciated.

  • over 5 years ago

    With the debug.xml for that build you can understand the stack and using the PC numbers see where it's happening.  You may also see it in the ERA reports with the stack already translated.

  • over 5 years ago in reply to jim_m_58

    Thanks

    How do you cross reference the PC in the crash report to those in the XML?

    The PC's above is - pc: 0x10000225

    But the XML starts at:-

    <entry filename="C:\\Users\\...MultiConfigApp.mc" id="3" lineNum="5" pc="268435456" symbol="initialize"/>
    <entry filename="C:\\Users\\...MultiConfigApp.mc" id="3" lineNum="6" pc="268435460" symbol="initialize"/>

    and continues up to

    <entry filename="C:\\Users\\...BaseProjectView.mc" id="24" lineNum="563" pc="268446570" 

    I am not seeing any ERA reports would these be produced for beta products?  Does it take some time for them to come through?  I have never used/seen these so it could be finger trouble?

  • over 5 years ago in reply to Robert

    Where you see pc= in the debug.xml, that is in decimal, while in the ciq_log, it's hex.  Convert the hex to decimal, and look in debug.xml.