You are currently reviewing an older revision of this page.

Bug Reports FAQ

Where can I report Connect IQ-related issues and feature requests to Garmin?

Connect IQ developers can report issues to the Connect IQ team with the Connect IQ Bug Reports tool. Please note that this tool is for reporting Connect IQ-related issues only. Any non-Connect IQ-related issues (e.g. Garmin Connect, Garmin Connect Mobile, Health API, FIT SDK, etc.) will be closed and we will suggest a more appropriate forum.

This tool functions in a similar way to the other discussion forums, but it provides a couple of added benefits:

  1. Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
  2. The Connect IQ team can maintain and update the status of a reported issue to give you some idea about whether we have a plan to fix the problem
  3. The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

What kind of issues should be reported?

Please let us know about anything related to Connect IQ app development and execution, including:

  • Problems with the SDK and development tools
  • Issues withe the Monkey C language
  • Problems with the Connect IQ APIs or related documentation
  • Inconsistencies between app execution in the Connect IQ simulator and on Garmin devices
  • Connect IQ app store problems
  • Garmin-published app crashes(typically an 'IQ!' icon will appear on the device screen when an app crashes)
  • Device crashes/reboots when running Connect IQ apps

Note that we cannot help address app crashes in apps not developed and maintained by Garmin. The best course of action is to contact the third-party developer using the Contact Developer link on their app's detail page on the app store.

What should I do before I report an issue with the Connect IQ Bug Reports tool?

Before reporting any issues, please be sure to try:

  • Updating or Installing the newest version of Eclipse or VS Code
  • Installing the latest version of the Connect IQ SDK, Eclipse plug-in, and VS Code extension
  • Updating the software of your Garmin Device (if using physical device)
  • Check for existing reports of the issue

What information should be included in a new issue report?

  • A Descriptive Title (e.g. "Simulator Freezes Launching App in VS Code")
  • The Environment:
    • Operating System or Device, including OS or software version of device
    • Connect IQ SDK version
    • Eclipse and plug-in version or VS Code Extension version
  • A detailed description of the issue
  • Steps to reproduce the issue
  • App source code or a code sample that can reproduce the issue (If you'd rather not share code publicly, please send an email to [email protected] with a link to your new thread and your source code attached)

We may not be able to effectively investigate a problem without the right info, so please provide as much information as possible. We'll follow up on the bug report if we need more information. Please note that if more information is requested, the issue will be marked completed if no response is received within 14 days of the request.

What should I do if I find my issue has already been reported?

  • Upvote the issue using the voting widget:
  • Add any new information about the issue to the existing report as a reply

What happens once an issue or suggestion has been reported?

  • Once an issue is reported, it will automatically be in an Under Review state, which means that it is in our queue to be investigated.
  • Once enough information is provided, the Connect IQ team will create an internal ticket to investigate the issue. At this point, the status will be updated to Ticket Created, and we'll include the internal ticket number in the status comment.
  • Once a fix or feature has been implemented, we will update the status to Complete and indicate the release in which the fix is available.
  • If a feature request will not be implemented, the status will be set to Not Planned. This primarily applies to feature requests–the only reason a bug report might not be planned is if it's a bug in a deprecated feature or for an old product that is no longer in maintenance.