Connect IQ Bug Reports - Connect IQ

This space is specifically for Connect IQ bug reports. Please review the Connect IQ Bug Reports FAQ before reporting a bug to be sure you have the information needed for Garmin to investigate the bug you wish to report.

Report Garmin Connect Web issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-web
Report Garmin Connect Mobile Android issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod
Report Garmin Connect Mobile iOS issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-ios
Product-related issues can be reported to either https://forums.garmin.com/outdoor-recreation/ or https://forums.garmin.com/sports-fitness/

Edge 850/550 data fields layouts

Stanislav.Bures
- Acknowledged on Oct 14, 2025
- 1 Comment
The real device supports many more data field layouts than the simulator. It is currently not possible to create full-screen data fields in SDK.
- Oct 13, 2025 11:44 AM
Instinct 3 Solar stuck in high power mode

ReedWorks
- Acknowledged on Oct 8, 2025
- 8 Comments
Firmware version: This has been reported with 10.36, but not with 9.21 Software affected: Any Connect IQ watch face, including Garmin's ones Expected behavior: 1. When wrist is raised (watch facing up), watch enters 'high power mode' (onExitSleep...
- Oct 8, 2025 4:28 AM
CIQ docs: "Managing monkey barrels" link at the top of Jungle Reference Guide is broken

flowstate
- Acknowledged on Oct 4, 2025
- 1 Comment
See comment for details.
- Oct 3, 2025 8:02 PM
Failure of derived class to call super.initialize() should be an error and not a warning, because this can break the type checker's "guarantees" and lead to run-time type errors

flowstate
- Acknowledged on Oct 3, 2025
- 3 Comments
The fact that it's only a warning leads to potential situations which break the type checker's guarantee that a member variable has a certain non-null type, leading to potential run-time errors. class Example { var thing as Float; function initialize...
- Oct 3, 2025 3:01 AM
Casting Float to Number does not yield Number

qlyoung
- Acknowledged on Oct 2, 2025
- 11 Comments
This code: var myFloat = 5.0; var myNumber = myFloat as Number; var mod = myNumber % 1; Compiles without warnings, but crashes at runtime with: Error: Unhandled Exception Exception: UnexpectedTypeException: Expected Number/Long, given Number/Float...
- Oct 2, 2025 1:07 AM
CIQ docs do not make it clear some new devices (e.g. Vivoactive 6) do not support onMenu(), and do require the use of View.setActionMenuIndicator(), in order to implement equivalent functionality (e.g. context-sensitive menu)

flowstate
- Acknowledged on Oct 2, 2025
- 2 Comments
Newer touch-first devices - Vivoactive 6, Venu 4 and Venu X1 - no longer have a dedicated menu button/touchscreen shortcut which triggers the onMenu behavior. In the past, *every* CIQ watch supported onMenu, whether by button short/long-press or a long...
- Oct 1, 2025 11:49 PM
CIQ device reference shows supported buttons for each device, but not touchscreen behaviors

flowstate
- Acknowledged on Oct 2, 2025
- 0 Comments
Overview https://developer.garmin.com/connect-iq/device-reference/ This is especially an issue in the context of the new touch-first devices (Vivoactive 6, Venu X1, Venu 4) which do not support onMenu at all. If I want to know which devices *do...
- Oct 1, 2025 11:37 PM
bug: datafield post-install flow

flocsy🤠
- Acknowledged on Oct 1, 2025
- 1 Comment
Brandon.ConnectIQ FYI I posted my "experience" of the new datafield post-install flow: https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-965/423182/bugs-in-datafield-post-install-flow fr965, FW: 25.04, CIQ 5.2.0, Connect IQ android...
- Sep 30, 2025 8:36 AM
bug / feature-request: ERA Viewer removes reports of "old" internal version when auto-migrated

flocsy🤠
- Acknowledged on Sep 30, 2025
- 0 Comments
1. developer uploads IQ file with version "1.0" (becomes internal version 1) 2. ERA Viewer displays 100 errors of app version "1.0" 2. Garmin auto migrates to internal version 2 (but correctly it's still called 1.0 for the users, developer!) 3....
- Sep 29, 2025 10:37 AM
SDK 8.3 Simulator App Crash with SYSTEM ERROR @ all widgets

TheMagician
- Acknowledged on Sep 28, 2025
- 4 Comments
The current SDK Simulator can't be used for all my widgets (watch faces are fine). When I start the simulator workflow the build is successful, the simulator app is started but then the widgets crash. It also crashes with any device that is selected...
- Sep 27, 2025 8:15 PM