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. 

  • Better stackoverflow debugging

    • Ticket Created on
    • 0 Comments
    E.g. following does lead to a stack overflow exception: endless recursion - of course, this is the obvious reason to many lines of code and/or functions - seems like functions are put on the stack and at some point the stack overflows The second...
  • Auto Lap Bug

    • Ticket Created on
    • 0 Comments
    In Eclipse, the simulator injects a new lap every mile by default. No way to disable that. Which is a problem when lap logic is part of the app and breaks the ability to perform particular use cases.
  • VSCode edit properties mishandles prompt

    • Ticket Created on
    • 0 Comments
    TO REPLICATE: 1. Build a data field project with a number of settings and include a text input that uses a prompt eg: <setting propertyKey="@Properties.tgt1" title="@Strings.tgt1Tit" prompt="@Strings.tgtPr"> <settingConfig type="alphaNumeric" errorMessage...
  • Hydration Tile in Connect (iOS) has a bug AND the Hydration Glance doesn't work at all

    • Ticket Created on
    • 0 Comments
    Hi, GARMIN CONNECT: When I try to add a cup (either using the +1 or just the +), it adds one up until 3 cups. Then, it starts acting weird. This is how it goes: [Using EITHER +1 cup button on the bottom OR the + sign to the right of the circle] 0...
  • Music player

    Former Member
    Former Member
    • Acknowledged on
    • 0 Comments
  • No info in doc how to check invalid sample from sensor history

    • Ticket Created on
    • 2 Comments
    I have a strange error on f6pro (but not in mine) Error Name: System Error in line x = MAT.round(v); where v is data field from Toybox.SensorHistory.SensorSample class I suppose data/v is invalid but how to check it? Doc says: The Sensor sample...
  • Better way to remove Null from types

    • Ticket Created on
    • 0 Comments
    I've been playing with the typechecker, and generally I like the results. One thing that seems problematic though is removing null from a type. This comes up a lot, especially with dictionaries. I can explicitly type a dictionary, but when accessing...
  • Inconsistent type checking of return values

    • Ticket Created on
    • 0 Comments
    function bar(arg as String) as Void {} function works(arg as String?) as String { return arg; } function fails(arg as String?) as Void { bar(arg); } The type checker is happy to accept a String or Null return value in a function returning...
  • simulation background event no current app in target combo box

    • Ticket Created on
    • 1 Comment
    I can see only one app i [Target App] and it's not that actually running in sim. What there is this option for? I can't imagine simulate background for app I don't actual test but ok, maybe somebody can test it injection of data when oother app starts...
  • Typos on the Persisting Data page.

    • Acknowledged on
    • 4 Comments
    On the Persisting Data page, in the "Accessing Properties and Settings: Application.Properties" section, in the API column of the table, it says Properties.getValue(), and Storage.setValue(). I'm pretty sure the latter should be Properties.setValue()...