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. 

  • Bug: navigating a course via System.exitTo fails if native activity is already running

    Lasse
    • Acknowledged on
    • 2 Comments
    Issue From a widget, I use System.exitTo(course.toIntent()) to start navigating a course using native activities such as hike. This works perfectly when there is no activity running. However, if there is already an activity running, then starting...

  • Body battery, pressure and heart history not returning values on D2

    1571716
    • Acknowledged on
    • 2 Comments
    Hi, I've got an user reporting that for his D2 device he has not got values for the body battery, the heart rate history and the pressure, I see that all these data have in common that they are taken from the Toybox.SensorHistory, I use the same example...

  • Compiler crash compiling null valued enum

    markw65
    • Acknowledged on
    • 3 Comments
    Not a big deal, but a proper error message would be nice. Otherwise, its hard to know what you've done wrong in a big file... Given: enum Foo { BAR = null } 4.1.5 and earlier crash with: ERROR: <device>: Could not parse Monkey C IR. 4.1.7...

  • Notification will not dismiss on watch if using Bubble Conversations on Android

    HookerOnTheRun
    • Acknowledged on
    • 0 Comments
    I've been having this problem where I will get a text, read the text both in the Bubble and in the app, the notification disappears on the phone, but persists on the watch. I'll dismiss the notification on my watch, and it will return within just a few...

  • FIT Write Bug

    DaveBrillhart
    • Acknowledged on
    • 16 Comments
    This is a bug related to rendering the FIT Write Data. A difference between Garmin Connect Mobile and Garmin Connect Web. I can't post an image here so I'll include it in the reply. In Garmin Connect Web, as I move the mouse to the right, values stop...

  • Garmin Instinct Crossover firmware bug: Alarm causes IQ watch face to switch to stock

    MobileDriveway
    • Acknowledged on
    • 4 Comments
    Multiple users (including myself) reported Connect IQ Watch Face apps switching to the Stock face after an Alarm on Crossover. The latest 3.11 firmware didn't help. It affects ALL Connect IQ watch face app. After an alarm the current watch face app...

  • utf-8 and string resources

    Tobi
    • Acknowledged on
    • 11 Comments
    i have a problem with german umlauts (öäü) in string resources: whenever i get the app from the ciq store (iq file) i only get "?" instead of umlauts while it works fine when i sideload the app or test in the simulator. this happened before (see https...

  • sdk-4.1.7 constant folds Symbol comparisons incorrectly

    markw65
    • Acknowledged on
    • 3 Comments
    With 4.1.7 at -O1 (the default) I tried: System.println(:foo == :foo); System.println(:foo != :foo); and got "false, true" as output. That looked wrong, so I tried: var x = :foo; System.println(x == x); System.println(x != x); and got...

  • bug: Bad layouts in simulator (approachs62, vivoactive3, vivoactive3d)

    flocsy🤠
    • Acknowledged on
    • 2 Comments
    Today I noticed that some devices have strange layouts in simulator. For example vivoactive3 has a layout called "3 fields B" that has a blue area in the top and the bottom (like wide-screen movies on an old TV) and there's only 1 actual field in the...

  • bug: some devices listed in docs as supports SensorHistory.getBodyBatteryHistory don't support it

    flocsy🤠
    • Acknowledged on
    • 0 Comments
    According to https://developer.garmin.com/connect-iq/api-docs/Toybox/SensorHistory.html#getBodyBatteryHistory-instance_function a) getBodyBatteryHistory is supported since API Level 3.3.0 b) supported on the following devices that don't have 3.3.0...