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. 

  • Are Glace dimensions in simulator trustworthy (correct?)

    Remoh
    • Acknowledged on
    • 0 Comments
    A few month ago, I reported that the glance dimensions on my real device (forerunner 255s) was not the same as in the simulator: https://forums.garmin.com/developer/connect-iq/i/bug-reports/simulator-bug-sdk-4-2-3-wrong-width-for-glanceview-in-fr255s...

  • getOldestSampleTime() and getNewestSampleTime() for stress history returns strange dates in simulator and actual device

    trudelta
    • Acknowledged on
    • 0 Comments
    getOldestSampleTime() and getNewestSampleTime() for stress history returns strange date years 1989 and 2043 in the simulator and on an actual device (tested only on a VA4S) Sample times on individual samples (SensorSample.when) seem correct.

  • VS Code plugin and simulator bugs

    Jeff
    • Acknowledged on
    • 2 Comments
    I've noticed 2 behaviors of the plugin that would be good to have fixed. 1) Often (always?) the first time the simulator is run the simulator window is displayed but the simulation does not start and the DEBUG CONSOLE in VS Code shows "Unable to connect...

  • Cannot upgrade apps when all installation slots full

    trudelta
    • Acknowledged on
    • 0 Comments
    In the Connect IQ app (iOS), app updates are queued but never get installed if all installation slots are full. There should be a warning message at least to tell the user to uninstall one app to be able to update.

  • Cannot Step Over/Into/Out in Monkey C after VS Code 1.79.0

    scletts
    • Ticket Created on
    • 2 Comments
    This looks like a repeat of the earlier Microsoft bug in VS Code I reported last month https://forums.garmin.com/developer/connect-iq/i/bug-reports/cannot-step-over-into-out-in-monkey-c-after-vs-code-1-78-0 It was fixed in Version 1.78.2 but has now...

  • SensorHistory.getOxygenSaturationHistory returns null on fēnix 7X PRO: 13.22

    nnkn
    • Acknowledged on
    • 4 Comments
    from era on my watchface : man of steel ~~~js Error Name: Unexpected Type Error Occurrences: 8 First Occurrence: 2023-06-28 Last Occurrence: 2023-06-28 Devices: fēnix® 7X PRO: 13.22 App Versions: 2023.06.28-2 Languages: chs Backtrace: getDFInfo.getSpo2...

  • New Crash on Vivoactive HR

    Jeff
    • Acknowledged on
    • 2 Comments
    This looks like the same problem that I reported in a bug report a month ago for the Forerunner 735xt which can be found here. The problem on the 735xt is not fixed though the bug report shows status "Complete". Here's the crash log from the Vivoactive...

  • Testing for NaN do not work when returned from a Math function

    SylvainGa
    • Acknowledged on
    • 1 Comment
    See this thread: https://forums.garmin.com/developer/connect-iq/f/discussion/338071/testing-for-nan/1637852#1637852 The following code snippet works var rad = NaN; System.println("rad == NaN: " + (rad == NaN)); // false System.println("rad.equals...

  • Please don't reset the time simulation between runs in the Simulator

    pstoppani
    • Acknowledged on
    • 0 Comments
    This feels like more of a bug than a feature request. If you set the time simulation to a specific time, the time is reset if you rerun the app. Like the Activity Data simulation I expect the Time Simulation to continue running between runs of the app...

  • CIQ Simulator shows "A debugging check in this application has failed" after upgrade Connect IQ SDK 4.2.4

    David Lin
    • Acknowledged on
    • 16 Comments
    After upgrade Connect IQ SDK, following error shows when I running CIQ emulator with fenix 7X But other device is fine. Does any anyone have clues to solve this problem? Connect IQ Device Simulator 4.2.4 2023/6/28: Update to SDK 6.2.0 is same.