Rediculously easy to cause device reboots with CIQ

Hi

I have been coding with CIQ recently and it seems to me that CIQ renders the device rediculously vulnerable to device reboots.

I have a simple data field that causes an immediate blue triangle when the activity start button is pressed (interestingly the simulator does not pick up the issue)

I am new to CIQ but not to coding - I think the last time I saw a device reboot during coding was writing 6510 assembler on the Commodore 64! 

I can fix my code, but it strikes me that anyone could write a datafield called 'Bomb!' and cause immediate reboots. I'm surprised CIQ isn't sufficiently sandboxed to isolate errors to the errant .PRG only

  • What device and what FW level?  What SDK?

    It's actually really hard to crash a device with CIQ.  This is the first case I've heard of in a number of years.  You may want to file a bug report and include the source for your app.

  • Fenix 6 Pro with 22.10

    Latest SDK (downloaded it on Monday this week)

    100% reproduceable. Start button then boom!

    I know what I am doing wrong (can stop the reboot by commenting out a few lines of code) but as I said I am super surprised it caused a reboot, this is a typical case you'd expect to see graceful exception handling.

  • What is the code you comment out to avoid the crash?  As I've said, crashing a device with CIQ is very, very uncommon.

    This strikes me as a FW issue, so it may only happen with the f6 devices.

  • Might not be sensible to post a code snippet that causes a reboot, but here is the callstack - I have been testing on the simulator with no issue, but this occurred while testing for the 1st time on a real device.


    3290 (fenix 6 Pro) SW ver: 2210
    Build Type: RELEASE
    Commit:c96a7bc00a3dd9df4aa849dbc6841b70c6483579
    ESN: 3352542644
    06/29/22 21:45:11
    RTL
    errnum: 0x00f
    r0: 0x20007520
    r1: 0x0457f8d1
    r2: 0x0006b6c8
    r3: 0x00000224
    r4: 0x000429c0
    r5: 0x000004f1
    r6: 0x006232b8
    Stack frame PC, SP: 0x00003383, 0x200071f0
    Call Stack - SP at 0x200071f0:
    0x000023f1
    0x00003a95
    0x0457f8d1
    0x0457f8d1
    0x0457f8d1
    0x0457f8d1
    0x00003da3
    0x0457f8d1
    0x000041c1
    0x0457f8d1
    0x0456f1d7
    0x04584b65
    0x047a1d27
    0x0456a121
    0x00057491
    0x00158eb3
    0x00053373
    0x0005ad0f
    0x0000556b
    0x00062c33
    0x00062e29
    0x00004a0d
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    0x00000000
    Uptime: 1303666382

  • do a bug report.  See the sticky about doing that, as there is also an email address where you can send your app to the Garmin CIQ group.

    See https://forums.garmin.com/developer/connect-iq/f/discussion/289584/connect-iq-developer-support

  • Have never seen or experienced this before either, care to share the code (even in pm) so I can see if this also happens on the FR955 for example? Really weird...

  • Please send the details of this crash, including the code snippets that you believe cause this crash, to [email protected]. We have many protections in place to prevent Connect IQ apps from crashing devices in this way, so if this is easily reproducible, we'd definitely want to get this fixed. Please reference this forum thread when you send the information.