Acknowledged
10 months ago

Watchface Crashes, but Sim and Preview are Working

Hi everyone,

I'm having an issue where my generated Watchface is crashing, but both SIM and the WatchfacePreview work like a charm.

Source Code (incl .prg) here:

https://github.com/r-neuschulz/HeartsDesire

Tested on Garmin Epix Pro 2 (Gen 2).

Steps to reproduce:

  1. Build the Project
  2. Load .prg file to Device
  3. Observe how the watchface defaults to a standard watchface, but the preview looks correct (like in the SIM).
Rxience
Parents
  • 10 months ago

    This kind of question is a good one for the main Discussion forum (https://forums.garmin.com/developer/connect-iq/f/discussion) since it sounds like there's additional debugging and investigation you can do. An app crash is usually due to a bug in the code that you'll need to address, while a device crash is more often a problem with Connect IQ that Garmin needs to address.

    I'd recommend seeing if someone can try this on another device (some developers in the community may be willing to help you out here) and see if the same thing occurs. It could be something that only affects certain products or it could be a problem with your particular device. jim_m_58's suggestion of adding println() statements is a good one, and we also have a debugger that's part of the VS Code extension you could leverage to try to narrow down the source of the problem. That, or there's always commenting out bits of code you suspect until you have something that works. Slight smile

    If you can demonstrate the problem is not in your code and you believe you can make a case for a Connect IQ bug, provide that info here and we can take a look. Also, review https://forums.garmin.com/developer/connect-iq/w/wiki/5/bug-reports-faq to make sure you're providing the info we need to investigate.

Comment
  • 10 months ago

    This kind of question is a good one for the main Discussion forum (https://forums.garmin.com/developer/connect-iq/f/discussion) since it sounds like there's additional debugging and investigation you can do. An app crash is usually due to a bug in the code that you'll need to address, while a device crash is more often a problem with Connect IQ that Garmin needs to address.

    I'd recommend seeing if someone can try this on another device (some developers in the community may be willing to help you out here) and see if the same thing occurs. It could be something that only affects certain products or it could be a problem with your particular device. jim_m_58's suggestion of adding println() statements is a good one, and we also have a debugger that's part of the VS Code extension you could leverage to try to narrow down the source of the problem. That, or there's always commenting out bits of code you suspect until you have something that works. Slight smile

    If you can demonstrate the problem is not in your code and you believe you can make a case for a Connect IQ bug, provide that info here and we can take a look. Also, review https://forums.garmin.com/developer/connect-iq/w/wiki/5/bug-reports-faq to make sure you're providing the info we need to investigate.

Children
No Data