Acknowledged
CIQQA-4638

field in dive app

Title:
Connect IQ Data Fields not available/selectable in native Dive activity on Descent Mk3i (firmware Host 25.21, GPS 14.01, CIQ 5.2.0)

Body:
Device: Descent Mk3i (51mm)
Firmware: Host 25.21 (46d5ea2), GPS 14.01, CIQ 5.2.0, BMX 21.1.0, Sensor Hub 35.10, Wireless 28.27

Issue:
Third-party Connect IQ Data Fields do not appear at all (not greyed out, simply absent) in the
field-selection list when configuring screens inside the native Dive activity. The same app
installs and runs correctly as a standalone Connect IQ watch app (type: watch-app) on the same
device/firmware, and Data Fields of the same type work normally in other activity types (e.g.
running). This appears to be a platform-level restriction specific to the Dive activity rather
than a bug in our app.

Context on why this matters:
We built and tested (on real Descent Mk3i hardware, not just the simulator) a Connect IQ app that
performs underwater dead-reckoning navigation: it tracks heading and estimated distance travelled
during a dive, stores the resulting path, computes an experimental return-to-origin guidance
vector back toward the dive's start point, and displays this live on-screen while diving. This
works well as a standalone watch app, but our intended design was to surface this navigation data
as an unobtrusive Data Field layered on top of Garmin's native Dive activity - keeping Garmin's own
depth, gas, NDL/decompression, and alarm handling fully intact and authoritative, with our field
only adding supplementary navigation info alongside it. The current platform restriction makes
that integration impossible, forcing a choice between our navigation feature and Garmin's native
dive-computer screens, rather than allowing both together.

Request:
Please allow third-party Connect IQ Data Fields to be added to screens within the native Dive
activity on Descent-series devices, the same way they're already supported in other activity
types. If there is a specific technical or safety reason Data Fields are currently excluded from
Dive activities, we'd appreciate documentation of that constraint so we can design around it
correctly.

Note: this app does not replace or modify any native dive-computer function (depth, gas, NDL/
decompression, alarms) and does not claim professional-grade navigation accuracy - it is an
experimental supplementary display only.