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. 

  • Live Tracking and CIQ applications

    • Ticket Created on
    • 3 Comments
    This is a bug that I could not find thread on. Starting a CIQ application session with GPS Enabled or Disabled the Connect Mobile App start a LiveTracking session. I tried this on several of my apps and also on a few others NON-GPS apps in the store...
  • ERA Backtrace points to a function that is never called

    • Ticket Created on
    • 7 Comments
    I was recently looking through some ERA backtraces and came across with a few that looked strange in two respects: 1) The backtrace consisted of only one line 2) The exception reference seemed to be impossible within the code that is pointed to by...
  • Warning prompt when submitting Contact Developer form with no email

    • Ticket Created on
    • 4 Comments
    Developers are frustrated that users can submit developer feedback without an email address, because the feedback they often receive is from users asking for help. The developers are left with no way to respond. We made an email address optional in the...
  • Eclipse Multi-Field Bug

    • Ticket Created on
    • 0 Comments
    I thought this was fixed. I'm running the latest Eclipse/Plugin and the latest SDK. When I render my data field in a multi-field view, only the last instance displays properly. Not a big deal.... since I only really need to see it in one field. But probably...
  • ERA: SDK 3.1.7, cyrillic names non-readable

    • Ticket Created on
    • 11 Comments
    Use SDK CIQ 3.1.7 and ERA. Log in with Developer credentials and observe Cyrillic names of the applications - distorted. Expected: - Possibility to select English names - Corrected Russian names in list.
  • in connectiq-sdk-win-3.1.7-2020-01-23-a3869d977 watchface diagnostics doesn't work

    • Ticket Created on
    • 5 Comments
    Hi In new SDK watch face diagnostic no more works. All is good in previous version
  • Activity.Info.currentHeading provides random numbers on Edge530

    • Ticket Created on
    • 2 Comments
    Activity.Info.currentHeading provides random numbers on Edge530. On any other device I tried (Edge 820, Fenix 5 / 6) same code works fine. It is not a problem of the device or the calibration as the heading on the map page is shown correctly. ...
  • Two Glaring API Gaps - Easy Additions

    • Ticket Created on
    • 2 Comments
    1. You already pull HR Zones. You are missing POWER Zones. The "pattern" already exists. The system call is essentially identical to HR Zones. It has been asked for for years. Please add the ability to pull POWER Zones into CIQ. Thanks. Our work around...
  • fenix 6 series firmware 6.0 causes watch face to crash

    • Ticket Created on
    • 10 Comments
    Hi, fenix 6 series users are reporting a crash while using the MagicDust watch face. ( https://apps.garmin.com/en-US/apps/2851d38b-22a8-41b6-84bf-2b0d4a229869 ) The crash report leads to the code logic where ActivityMonitor.getInfo().floorsClimbed returns...
  • obscurity flags wrong on Fenix 6 pro device but ok in sim

    Former Member
    Former Member
    • Ticket Created on
    • 9 Comments
    i've got a user on a Fenix 6 Pro, firmware 6.0, who is getting a value of "0" in the getObscurityFlags(); when displaying a datafield in the full screen layout. in the sim, i properly get a 15. any thoughts? code is more or less as below function...