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: makeWebRequest unable to handle a 401 HTTP response with empty response body

    • Acknowledged on
    • 1 Comment
    when a web service returns a response with an empty body, makeWebRequest returns with a -400 response code ( Response body data is invalid for the request type). I have tried all available HTTP reponse content types but nothing works. This problems happens...
  • Configuration not allowed in beta watchface through Connect IQ app

    • Acknowledged on
    • 3 Comments
    The Connect iq application on my smartphone does not allow configuration on the beta watchfaces that I am developing and have installed on my device. There has been some changes? before if it could be done. Please solve It, for me its the best way to...
  • Garmin Express overwriting case sensitive properties

    • Acknowledged on
    • 5 Comments
    Properties with the same id in properties.xml that start with a lowercase letter or an uppercase letter, e.g. ("m"/"M", "x"/"X") are overwritten by Garmin Express with the value of the uppercase letter property as soon as the settings are opened via Express...
  • Garmin Trial App API doesn't work

    • Acknowledged on
    • 6 Comments
    I can't communicate with the server, it always returns 404 error when I try to unlock an APP. I've been trying with the example URL and it's always the same error
  • BUG REPORT: Invalid accelerometer data with SensorLogger

    • Acknowledged on
    • 1 Comment
    Hi all. I have several problems while logging to a FIT file inertial data on my Felix 6 Pro (Firmware 26.00) by using the SensorLogging class. The issues are the following: The timestamp field of the Accelerometer Data table is completely bugged:...
  • Feature Request- Stress alert, sleep coach, load focus on instinct 2x solar tactical

    • Acknowledged on
    • 1 Comment
    Hoping that stress alert, sleep coach, nap detection and load focus on the watch itself can be added on instinct 2x solar tactical. It just feels like the garmin developers had forgotten the instinct line up already after just several months. No significant...
  • Confusing definition of LightNetwork.getBikeLights() in API documentation

    • Acknowledged on
    • 0 Comments
    In API documentation (and also in SDK) it is: getBikeLights () as Lang.Array < AntPlus.LightNetworkState > or Null But it returns an Array of BikeLight. When type check level is set to strict you need to do a lot of workaround code to handle this...
  • Bug report: ANT GenericChannel.release causes issues with other channels

    • Acknowledged on
    • 4 Comments
    In our app we have 3 ANT generic channels. One is a master, two are slaves. I am trying to change one of the channels to a BackgroundScan channel. To do that I have to firstly switch it to a "Ant.CHANNEL_TYPE_RX_ONLY" type. To do that I have to reinitialise...
  • Connect IQ fields are missing on Lap view on API Level 5

    • Acknowledged on
    • 8 Comments
    Since the update to Api level 5 the Connect IQ fields disappeared from the Laps overview. I've started a thread about this with more information and trying to figure out how to solve this. I've tested with 2 api versions Venu 2 Plus (4.2.4) and Venu...
  • Parser issue with parenthesized array assignment expressions

    • Acknowledged on
    • 0 Comments
    Given a function foo() that returns an array, you can write foo()[1] = 42; and the compiler accepts it. but (foo() as Array<Number>)[1] = 42; is a parser error. And so is (foo())[1] = 42; ...: no viable alternative at input '(foo())[1...