Acknowledged
CIQQA-3954

BUG: Connect IQ Data Fields Not Persisting on Navigation Screens

Hello,

I'm experiencing a persistent issue with Connect IQ data fields on my Garmin Fenix 7 Pro specifically related to navigation screens.

Problem Description:

When I add a Connect IQ data field to a navigation screen, it appears correctly during configuration. However, when I start a new activity with navigation enabled, the Connect IQ field is automatically replaced by the default Timer field.

Steps to Reproduce:

  1. Go to Navigation Settings → Data Screens
  2. Add an additional navigation screen
  3. Add a Connect IQ data field to this screen (any Connect IQ field)
  4. Save and exit
  5. Start a new activity with navigation enabled
  6. Result: The Connect IQ field has been replaced by Timer

What Works:

  • Connect IQ fields work perfectly on regular activity screens (non-navigation)
  • Native Garmin data fields persist correctly on navigation screens
  • The configuration appears saved until the activity is restarted (if go to navigation settings during an activity)

What I've Tried:

  • Multiple different Connect IQ data fields from the store
  • Developing my own custom data field using Connect IQ SDK 5.2 with API Level 5.2
  • Latest firmware version on Fenix 7 Pro
  • Removing and re-adding the fields
  • Different activity profiles

Device Information:

  • Model: Fenix 7 Pro
  • Firmware version: 25.11

Question:

Is this a known bug? Are navigation screens supposed to support Connect IQ data fields, or is this a limitation? It seems inconsistent that native fields persist but Connect IQ fields don't.

Any workaround or fix would be greatly appreciated.

Thank you!

gregarno
  • in reply to flocsy🤠

    OK, so its even worse on fr965:

    From the watch face: Menu > Activities & Apps > Navigate > Navigate Settings > Data screens > Add new > Custom Data > Field 1 > Connect IQ Fields > Choose a full screen datafield > it asks to reorder them > done

    As I click Done I am on a 2 Field screen with Lap Distance and Lap Time.

    I tried this 3 times, with and without reordering with 2 different CIQ datafield. So it's crap. I wonder though if this is the right place to report it or in Garmin Customer support for the specific devices. Let's see what others will comment here. I'm reporting it now, though the chance it'll be fixed on fr965 is not high.

  • Ok, so maybe this is a slightly different bug, though from what I understand the bug seems to be very similar with the distinction that it happens 100% of the time in your device on navigation screens, while the "regular" bug (any activity's regular screens) it doesn't happen 100% of the time.

    I don't use the watch for navigation. Can you update the description to be more precise how to reproduce it? Should I enter run and then Menu and then navigation? Or should I go into the activity called Navigation (I'm on fr965)?

  • in reply to flocsy🤠

    Thanks for your reply.

    Just to clarify: I do not have this issue on regular activity screens - Connect IQ data fields work perfectly fine there and persist correctly between activities.

    The problem is exclusively with navigation screens. When I configure a Connect IQ data field on a navigation-specific screen, it gets reset to the default Timer field every time I start a new activity with navigation enabled.

    I've also tested on a Garmin Epix Pro Gen 2 and encountered the exact same behavior.

    This is particularly frustrating because these watches aren't that old, yet they're no longer receiving new native feature updates. The whole point of Connect IQ is to allow users and developers to add functionality that Garmin doesn't provide natively anymore. But if Connect IQ fields can't even be reliably saved in navigation screens, it defeats the entire purpose of the platform.

  • This is a known bug. I first reported it 5 years ago on fr245, then fenix6, then fr965. Garmin never even attempted to fix it. They don't even think it's a bug. Every time I reported it they said that's the 1st time anyone ever reported it. And it's not related to navigation, it happens on any datafield screen with any CIQ datafield.