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: forum: can't post less-than or greater-than signs

    • Acknowledged on
    • 2 Comments
    it's impossible to post less-than or greater-than signs in an ORIGINAL post (like this, even though it's possible in comments)
  • bug: app trials documentation page has invalid example OR simulator bug

    • Acknowledged on
    • 4 Comments
    On this page: https://developer.garmin.com/connect-iq/core-topics/trial-apps/ there's an example manifest: See in 1st comment, can't post here however this example is invalid or probably more precisely misleading, because it won't work with any...
  • SERIOUS BUGS - SDK 4.2.1

    • Acknowledged on
    • 22 Comments
    Building with SDK 4.1.7 my app looks and acts as expected. My current release on the app store is built with this SDK. Building with SDK 4.2.1 most of the graphics on my app do not appear as they have up till this SDK release. Also... when building...
  • CIQ app crashes on Instinct 2 when resource is used in ActionMenuItem

    • Acknowledged on
    • 1 Comment
    Hi, I have found interesting CIQ crash with instinct 2. The following code results in app crash, when I try to create instance of MainMenu class import Toybox.WatchUi; class MainMenu extends WatchUi.ActionMenu { function initialize () { ActionMenu...
  • onExitSleep() no longer called after user sleep time (FW 25.00, Fenix 6)

    • Acknowledged on
    • 3 Comments
    Hello, this bug has reappeared for Fenix 6 after Firmware update 25.00. In the daytime, onEnterSleep() and onExitSleep() are triggered by wrist gesture as normal. But once we enter the user's sleep period, onExitSleep() is never called again. Even...
  • Fix the static functions

    • Acknowledged on
    • 5 Comments
    Hi CIQ team, The static functions are broken for a long time now, it would be a good thing to fix them and be able to use them as in other languages Best regards
  • Eclipse - SDK new devices update caused 'Index out of bounds' error in Run debug configuration.

    • Acknowledged on
    • 7 Comments
    Hello, All worked normally in Eclipse 2022.12, SDK 4.1.7. Win 10 x64. New devices arrived : forerunner 965 and 265/265s. SDK devices were updated. Now IDE cannot launch debugger. Configuration for run debug now totally damaged. An error has occurred...
  • Feature request: WatchUi.showToast() for Background service

    • Acknowledged on
    • 1 Comment
    In API exists only one method for user attension: Background. requestApplicationWake. I suppose it's a good alternative to add method Background.showToast().
  • feature-request: managing of memory connecting with settings

    • Acknowledged on
    • 1 Comment
    Everybody knows how important is memory consumption, especial in glance, background and watch faces, so 1. Add scope to individual properties in settings (like with resources). Of course updating property in glance doesn't destroy others from foreground...
  • sdk 4.2.1 memory consumption

    • Acknowledged on
    • 15 Comments
    eclipse, win widget f6p - 4.1.7 11kB - 4.2.1.16.5kB +6,5kB on start!!!! 6.5kB/28kB almost 25% more memory just because using 4.2.1.... so if glance uses e.g. a bigger properties (has to be the same, no scope), the same like app usually crash...