Bug Reports FAQ

Brandon.ConnectIQ — Wed, 28 Feb 2024 20:35:22 GMT

Current Revision posted to Wiki by Brandon.ConnectIQ on 2/28/2024 8:35:22 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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.

Report Garmin Connect Web issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-web
Report Garmin Connect Mobile Android issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod
Report Garmin Connect Mobile iOS issues to https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-ios
Product-related issues can be reported to either https://forums.garmin.com/outdoor-recreation/ or https://forums.garmin.com/sports-fitness/

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 Connect IQ SDK and development tools
Issues with 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 Connect IQ 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 firmware version of device
- Connect IQ SDK version
- VS Code Extension version
- VS Code version
A detailed description of the issue
Steps to reproduce the issue
Images or videos that demonstrate the issue as appropriate
App source code or a code sample that can reproduce the issue

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.

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 Acknowledged.

Bug Reports FAQ

Brandon.ConnectIQ — Fri, 13 Oct 2023 18:56:29 GMT

Revision 14 posted to Wiki by Brandon.ConnectIQ on 10/13/2023 6:56:29 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

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 Connect IQ SDK and development tools
Issues with 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 Connect IQ app crashes (typically an 'IQ!' icon will appear on the device screen when an app crashes)
Device crashes/reboots when running Connect IQ apps

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 firmware version of device
- Connect IQ SDK version
- VS Code Extension version
- VS Code version
A detailed description of the issue
Steps to reproduce the issue
Images or videos that demonstrate the issue as appropriate
App source code or a code sample that can reproduce the issue

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.

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 Acknowledged.

Bug Reports FAQ

Brandon.ConnectIQ — Tue, 05 Jul 2022 17:20:31 GMT

Revision 13 posted to Wiki by Brandon.ConnectIQ on 7/5/2022 5:20:31 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

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 Connect IQ SDK and development tools
Issues with 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 Connect IQ app crashes (typically an 'IQ!' icon will appear on the device screen when an app crashes)
Device crashes/reboots when running Connect IQ apps

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 firmware version of device
- Connect IQ SDK version
- Eclipse and plug-in version or VS Code Extension version
- Eclipse version or VS Code version
A detailed description of the issue
Steps to reproduce the issue
App source code or a code sample that can reproduce the issue

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.

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 Acknowledged.

Bug Reports FAQ

Brandon.ConnectIQ — Mon, 04 Apr 2022 22:05:48 GMT

Revision 12 posted to Wiki by Brandon.ConnectIQ on 4/4/2022 10:05:48 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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:

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
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 ConnectIQ@garmin.com 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.

Bug Reports FAQ

Brandon.ConnectIQ — Wed, 30 Mar 2022 13:27:34 GMT

Revision 11 posted to Wiki by Brandon.ConnectIQ on 3/30/2022 1:27:34 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse 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 ConnectIQ@garmin.com 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.

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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Mon, 28 Feb 2022 14:08:14 GMT

Revision 10 posted to Wiki by Brandon.ConnectIQ on 2/28/2022 2:08:14 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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 will be closed and possibly moved to a more appropriate forum.

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse 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 ConnectIQ@garmin.com 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.

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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Mon, 28 Feb 2022 14:05:21 GMT

Revision 9 posted to Wiki by Brandon.ConnectIQ on 2/28/2022 2:05:21 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What kind of issues should be reported?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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 will be closed and possibly moved to a more appropriate forum.

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse 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 ConnectIQ@garmin.com 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.

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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Wed, 09 Sep 2020 17:03:26 GMT

Revision 8 posted to Wiki by Brandon.ConnectIQ on 9/9/2020 5:03:26 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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 will be closed and possibly moved to a more appropriate forum.

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse 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 ConnectIQ@garmin.com 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.

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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Stephen.ConnectIQ — Tue, 09 Apr 2019 14:19:44 GMT

Revision 7 posted to Wiki by Stephen.ConnectIQ on 4/9/2019 2:19:44 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What should I do before I report an issue with the Connect IQ Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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. This tool functions in a similar way to the other discussion forums, but it provides a couple of added benefits:

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse Version
A detailed description of the issue
Steps to reproduce the issue
Any applicable additional information
A code sample that can reproduce the issue
- If you'd rather not share code publicly, please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

_{*Please note that this tool is for reporting Connect IQ-related issues only. Any non-Connect IQ-related issues will be closed and possibly moved to a more appropriate forum.}

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.
The Connect IQ team will create an internal ticket to verify 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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Stephen.ConnectIQ — Tue, 09 Apr 2019 14:17:53 GMT

Revision 6 posted to Wiki by Stephen.ConnectIQ on 4/9/2019 2:17:53 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What should I do before I report an issue with the Connect I Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse Version
A detailed description of the issue
Steps to reproduce the issue
Any applicable additional information
A code sample that can reproduce the issue
- If you'd rather not share code publicly, please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

_{*Please note that this tool is for reporting Connect IQ-related issues only. Any non-Connect IQ-related issues will be closed and possibly moved to a more appropriate forum.}

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.
The Connect IQ team will create an internal ticket to verify 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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Tue, 09 Apr 2019 13:27:45 GMT

Revision 5 posted to Wiki by Brandon.ConnectIQ on 4/9/2019 1:27:45 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What should I do before I report an issue with the Connect I Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse Version
A detailed description of the issue
Steps to reproduce the issue
Any applicable additional information
A code sample that can reproduce the issue
- If you'd rather not share code publicly, please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

_{*Please note that this tool is for reporting Connect IQ-related issues only. Any non-Connect IQ-related issues will be closed and possibly moved to a more appropriate forum.}

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 and issue is reported, it will automatically be in an Under Review state, which means that it is in our queue to be investigated.
The Connect IQ team will create an internal ticket to verify 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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Mon, 08 Apr 2019 22:09:24 GMT

Revision 4 posted to Wiki by Brandon.ConnectIQ on 4/8/2019 10:09:24 PM

Where can I report Connect IQ-related issues and feature requests to Garmin?
What should I do before I report an issue with the Connect I Bug Reports tool?
What information should be included in a new issue report?
What should I do if I find my issue has already been reported?
What happens once an issue has been reported?

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

Others having a similar issue can upvote an issue to raise Garmin's awareness of the problem
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
The status tracks the time since the last status change, which should help the Connect IQ team stay accountable

While not a full ticket tracking system, this should be a significant improvement over our past attempts to track reported issues in regular discussion threads, which became difficult to manage!

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

Before reporting any issues, please be sure to try:

Updating or Installing the newest version of Eclipse
Installing the latest version of the Connect IQ SDK and Eclipse plugins
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 Eclipse")
The Environment:
- Operating System or Device, including OS or software version of device
- Connect IQ SDK version
- Eclipse Version
A detailed description of the issue
Steps to reproduce the issue
Any applicable additional information
A code sample that can reproduce the issue
- If you'd rather not share code publicly, please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

_{*Please note that this tool is for reporting Connect IQ-related issues only. Any non-Connect IQ-related issues will be closed and possibly moved to a more appropriate forum.}

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 and issue is reported, it will automatically be in an Under Review state, which means that it is in our queue to be investigated.
The Connect IQ team will create an internal ticket to verify 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.
After an issue has been verified, it will be prioritized within one business week. Prioritization is indicated by one of three status types:
- Coming Soon - This is a high priority issue for which we are implementing the related fix or feature and will include it in a future release
- Future Consideration - This is a lower-priority issue for which we understand the issue and will consider a fix or feature addition in a future release
- Not Planned - This request will not be implemented. 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 on an old product that is no longer in maintenance.
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.

Bug Reports FAQ

Brandon.ConnectIQ — Wed, 03 Apr 2019 22:14:57 GMT

Revision 3 posted to Wiki by Brandon.ConnectIQ on 4/3/2019 10:14:57 PM

Why does this tool exist?

For a time we have simply taken reports of bugs from our developers through our general forums. This was effective in the beginning, however, Connect IQ is a growing platform, currently with over 1,000 developers. This growth has no signs of slowing down. It's our intent to provide our developers with the best set of tools possible to develop on our platform. For this we need options that are scalable and easily tracked. Having a unique tool for bug report meets our needs.

Due to the nature of this tool the Connect IQ team will be taking a more active role in moderating the content within it. You can expect us to actively track bugs reported, update threads with new info regarding issues as it becomes available, and actively moderate threads. In this tool it is important that we can gain and provide pertinent information. Any threads not following the rules of the forum may be deleted, closed, or moved to an appropriate forum.

Bug Reporting Rules

This tool is only used to report Connect IQ bugs. Any general questions will either be deleted, closed, or moved to the appropriate forum.
Before reporting any bugs please ensure that you have tried:
- Updating or Installing the newest version of Eclipse
- Installing the latest version of the Connect IQ SDK and Eclipse plugins
- Updating the software of your Garmin Device (if using physical device)
- Check the forums for existing reports of the bug
If a bug has already been reported, add any new information about the bug to the existing report as a reply.
Bugs reported must contain the following information:
- A Descriptive Title (e.g. "Simulator Freezes Launching App in Eclipse")
- The Environment:
  - Operating System or Device (including OS number or Software version of device)
  - Eclipse Version
- A detailed description of the issue
- Steps to reproduce the issue
- Any applicable additional information
- A code sample that can reproduce the issue (in email only if preferred)
Once bug is created please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

We are excited to ramp up our ability to better serve our developers when it comes to our bug reporting and tracking abilities! Thank you all so much for the time, effort, and help in continuing to shape the fastest growing Smart Wearable platform on the market.

How to Use This Tool

Bug Reports

Brandon.ConnectIQ — Wed, 03 Apr 2019 22:08:42 GMT

Revision 2 posted to Wiki by Brandon.ConnectIQ on 4/3/2019 10:08:42 PM

Bug Reporting Rules:

Welcome to our Connect IQ bug reporting tool. This Wiki is intended to help you understand why it exists as well as its rules and the expectations.

Why does this tool exist?
For a time we have simply taken reports of bugs from our developers through our general forums. This was effective in the beginning, however, Connect IQ is a growing platform, currently with over 1,000 developers. This growth has no signs of slowing down. It's our intent to provide our developers with the best set of tools possible to develop on our platform. For this we need options that are scalable and easily tracked. Having a unique tool for bug report meets our needs.

What are the Rules and Expectations for this forum?
Due to the nature of this tool the Connect IQ team will be taking a more active role in moderating the content within it. You can expect us to actively track bugs reported, update threads with new info regarding issues as it becomes available, and actively moderate threads. In this tool it is important that we can gain and provide pertinent information. Any threads not following the rules of the forum may be deleted, closed, or moved to an appropriate forum.

Rules:

This tool is only used to report a BUG. Any general questions will either be deleted, closed, or moved to the appropriate forum.
Before reporting any bugs please ensure that you have tried:
- Updating or Installing the newest version of Eclipse
- Installing the latest version of the Connect IQ SDK and Eclipse plugins
- Updating the software of your Garmin Device (if using physical device)
- Check the forums for existing reports of the bug
If a bug has already been reported, add any new information about the bug to the existing report as a reply.
Bugs reported must contain the following information:
- A Descriptive Title (e.g. "Simulator Freezes Launching App in Eclipse")
- The Environment:
  - Operating System or Device (including OS number or Software version of device)
  - Eclipse Version
- A detailed description of the issue
- Steps to reproduce the issue
- Any applicable additional information
- A code sample that can reproduce the issue (in email only if preferred)
Once bug is created please send an email to ConnectIQ@garmin.com including a link to your new thread and the code sample to reproduce

Once we receive the email, we will create a ticket, verify the issue, and prioritize the ticket. Each ticket is unique and some will take priority over others depending on the severity. However, each ticket should be prioritized within one work week (usually shorter--exception for observed work holidays).

We are excited to ramp up our ability to better serve our developers when it comes to our bug reporting and tracking abilities! Thank you all so much for the time, effort, and help in continuing to shape the fastest growing Smart Wearable platform on the market.

-The Connect IQ Team

Bug Reports

Former Member — Fri, 29 Mar 2019 20:08:10 GMT

Revision 1 posted to Wiki by Former Member on 3/29/2019 8:08:10 PM

This is a placeholder for information about our bug reports Wiki.