Acknowledged
1 day ago
CIQQA-3487

Critical Bug Report: Custom Data Fields Stop Running After Entering a Custom Glance (Instinct 3 Solar 45mm, FW 10.26)

Device: Garmin Instinct 3 Solar 45mm
Firmware: 10.26
CIQ Version: Current as of firmware 10.26

When running an activity with a Custom Data Field (DF), if the user exits to the glance carousel and enters any Custom Glance, upon returning to the activity screen, the Custom DF(s) stop running and display only the icon placeholder. They resume only after the activity is stopped and restarted.

This does not happen if:

  • A Custom DF is running and the user enters only stock glances, or

  • A stock DF is running and the user enters a Custom Glance.

Steps to Reproduce

  1. Load a Custom DF into an activity (tested with Running, Field 2 - main window).

    • Field 1 can be any DF - it's the small window.

  2. Ensure one or more Custom Glances are loaded in the glance carousel.

  3. Start the activity.

  4. During the activity, enter the glance carousel (via watch face, Back button, or HotKey).

  5. Enter a Custom Glance (depth does not matter).

  6. Exit the glance (via any method).

  7. Return to the activity (via Start button).

  8. Observe: Custom DF(s) are no longer running, showing only their app icon.

Only a stop and start of the activity revives the DF(s).

Tested Configurations

  • Custom DFs tested:

    • Instinct Runner (karrth)

    • Hiker DF (flocsy)

    • Pacing (jenshansen)

  • Custom Glances tested:

    • TR03 (karrth, beta)

    • Weight Widget (HarryOnline)

    • Open Weather Widget (MobileDriveway)

  • Controls:

    • Using stock glances - Custom DFs behave normally.

    • Using stock DFs - behave normally after Custom Glances.

This suggests the problem is not app-specific but in the lifecycle interaction between CIQ Data Fields and CIQ Glances on Instinct 3.

Additional Notes

  • No CIQ_LOG.yml entries are created in /GARMIN/APPS/LOGS/.

  • The problem is reproducible across multiple DFs and Glances.

  • The issue does not appear memory-related; it looks like a lifecycle/context-handling bug when returning from CIQ Glances to an activity with CIQ Data Fields.

  • Related forum reports note that Instinct 3 glances sometimes misbehave and that CIQ DFs can fail to redraw after state transitions (e.g. pause/resume, “Resume Later”). This seems to be a new variation specific to the DF - Glance interaction.

  • This has been tested on release and beta firmware.

Impact and Request.

This is a significant usability problem for an outdoors-oriented watch. During an activity (e.g., hiking, running, climbing), a user may need to check glance data (weather, battery, widgets) but currently doing so silently disables all custom DFs until the activity is restarted, leading to loss of critical data tracking mid-session.

Please investigate whether the CIQ DF lifecycle is being terminated or improperly resumed after entering/exiting CIQ Glances on Instinct 3. If possible, provide a firmware or CIQ update that preserves DF execution state across Custom Glance transitions. Thank you.

I have attached attachments to my two Github repositories with a basic Custom App/Glance and Custom DF to replicate the issue. Each contains the code and also a PRG file that can be sideloaded for ease.

https://github.com/Karth01/GarminDFBugTest.git

https://github.com/Karth01/GarminGlanceBugTest.git

karrth