Wiki

New Developer FAQ

Brandon.ConnectIQ — Mon, 03 Mar 2025 15:52:03 GMT

Current Revision posted to Wiki by Brandon.ConnectIQ on 3/3/2025 3:52:03 PM

Where can I download the SDK?
How do I get started with Connect IQ?
I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?
Am I allowed to charge for my app though the Connect IQ app store?
Can I display seconds on my watch face?
How do I format output padded with leading zeros?
How can I load the apps I develop to my device for testing purposes?
I have side-loaded an app as described above, but app settings won't work. Why is this?
My app uses app settings, and it sometimes crashes after changing the settings, but the rest of the time it works fine. What can cause this?
I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?
How can I test or debug Connect IQ apps I am developing?
I think that I've found a bug with CIQ. How do I report it?

Where can I download the SDK?

The latest version of the SDK can be found at http://developer.garmin.com/connect-iq/sdk/.

How do I get started with Connect IQ?

The Connect IQ Basics Guide is a good place to start gaining familiarity with Monkey C and Connect IQ.
Once you're set up, take a look at the Core Topics and User Experience Guide for more in-depth info.
API Documentation and more Monkey C specifics are also available on our developer site.
The SDK includes a set of sample apps in the 'samples' folder that demonstrate some of the basic capabilities of Connect IQ.

If you have questions along the way, these forums are the best place to go for assistance. Many questions have already been answered in previously posted threads, however both the Connect IQ team and several experienced developers monitor the forums to answer new questions or respond to issues you may encounter.

I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?

Yes! We have designed the SDK so that you can target any Connect IQ-compatible devices, regardless of the Connect IQ version they support. A project can be configured to target a minimum SDK version, which limits the selectable target devices to those that support the selected Connect IQ version. Targeting the newest version of Connect IQ will limit the devices that can run your app, but will give you access to all of the latest goodies. Anything built targeting earlier SDK versions will work on the latest devices, so allows your app to run on more devices as long as you don't need the newest features for your app.

The minimum SDK selector is designed to build for the highest supported SDK for each device. For example, consider this set of devices: device A (3.x), B (2.x), and C (1.x). The table below illustrates how the build system is designed to function:

Minimum SDK Selected	Eligible Target Devices	What Gets Built
3.0.x	A	3.0.x PRG for A
2.4.x	A, B	3.0.x PRG for A, 2.4.x PRG for B
1.2.x	A, B, C	3.0.x PRG for A, 2.4.x PRG for B, 1.2.x PRG for C

Am I allowed to charge for my app though the Connect IQ app store?

Yes, you are! Garmin offers a monetization solution that allows you to accept payments for your apps directly through the App Store. You can read more about it in the Monetization docs.

It is also acceptable to list prices, link to payment sites, or ask for donations on the Connect IQ app store as long as solicitations are related to your app and you mark that the app requires payments, etc., in the app listing details.. The app store falls under the the Connect IQ SDK License Agreement, which does not forbid solicitation for sales of apps by app developers. However, solicitation for business on Garmin sites other than the app store (such as this forum) is prohibited but Garmin's Terms of Use.

Can I display seconds on my watch face?

Yes, you can! However, one priority of Connect IQ is the preservation of battery life, so we have a system in place that governs how often watch faces may be updated. Generally, watch faces update once per minute in low power mode, and once per second when in full power mode. The watch will enter full power mode for a few seconds when the user gestures to look at it, and then returns to low power mode. Developers will often detect this transition to full power mode, display a seconds indicator for a few moments, and then hide the seconds indicator once the device returns to low power mode. Newer devices may also support Always On watch faces, which can update once per second as long as they operate within certain limits.

You can find out more about low power mode, full power mode, and Always On watch faces in the Connect IQ Basics Guide, or read about the related APIs in the API Docs.

How do I format output padded with leading zeros?

Many Connect IQ apps include time values that require leading zeros. For example, time written in an HH:MM:SS format appears as "12:05:05" rather than "12:5:5". Monkey C includes string formatting functions that can get this job done using a %02d format specifier.

A common error is to specify a format of %.2d or %0.2d. This may pad a decimal with leading zeros in some languages, such as in C++'s printf() function, but Monkey C follows the C99 standard. C99 requires the 0 flag to specify padding with leading zeros for d, i, o, u, x, X, a, A, e, f, F, g, and G conversions. In addition, C99 states that if a precision is specified with '.', the the 0 flag is ignored.

How can I load the apps I develop to my device for testing purposes?

Apps are typically installed to devices via the Connect IQ App Store, but it's often useful to side-load an app to a device for testing without having to first upload a version to the app store. Here's how (this assumes you already have the Monkey C Visual Studio Code Extension installed):

In Visual Studio Code, choose View > Command Palette...
Select Monkey C: Build for Device
Select the target product from the device list
Choose an output location for the build
Select either Debug or Release depending on your intent (either will build a PRG that will run on a device)
Connect your device to the computer via USB (it should appear as a drive)
Copy the PRG file from the output location to /GARMIN/APPS on your device
Disconnect your device; the app should be available for use

I have side-loaded an app as described above, but app settings won't work. Why is this?

App settings allow user to configure an app via the Connect IQ Store app, Garmin Express, or Garmin Connect Mobile, and depend on the Connect IQ App Store to function properly. When an app is side loaded, this connection to the Connect IQ App Store is never established. If you have an app that uses app settings that needs to be tested, you may submit the app to the Connect IQ App Store and test out the settings features while the app is either in a beta state or pending approval.

My app uses app settings, and it sometimes crashes after changing the settings, but the rest of the time it works fine. What can cause this?

In the past, there have been issues where the client used to manage app settings, like the Connect IQ Store app, Garmin Express, or Garmin Connect Mobile, has returned a setting value with an unexpected type, so it's good practice to check a setting value to ensure it's the expected type. For example, this code will check for a null value and convert the value to a Number as long as it is not null. Otherwise, a default value is returned:

function readKeyInt(myApp,key,thisDefault) {
    var value = myApp.getProperty(key);
    if(value == null || !(value instanceof Number)) {
        if(value != null) {
            value = value.toNumber();
        } else {
            value = thisDefault;
        }
    }
    return value;
}

I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?

We added a a feature in the 2.1.2 SDK release to perform an argument count check on function and method calls. This was included as part of a larger security effort, which includes things like app signing and encryption of app data. Overall, this is a good thing, since it promotes more robust source code prevents some potential security exploits. Unfortunately, it has also caused some apps to crash on 1.3.x and 2.x devices when built with the 2.1.2 SDK even though these same apps execute without issue when built with earlier SDK releases. This kind of crash appears in the CIQ_LOG.TXT or CIQ_LOG.YML file as a Too many arguments error, signifying the argument count check has failed. Here are a couple of examples that illustrate potential causes:

Missing state arguments for the onStart() and onStop() methods. These are currently unused arguments and were passed implicitly in earlier versions of Connect IQ, but must now be included explicitly.
An initialize() method that takes an array of options but to which none are passed.

How can I test or debug Connect IQ apps I am developing?

A simple way to test Connect IQ apps is to include System.println() statements at strategic points in your app. Within Eclipse, these statements will output to the console. On a device, these statements write to the /GARMIN/APPS/LOGS<APPNAME>.TXT file, if it exists. This file is not automatically created, so must be created manually and named to match the name of the app's PRG file. For example, to log output from /GARMIN/APPS/MYAPP.PRG, create the /GARMIN/APPS/LOGS/MYAPP.TXT file.

For more advanced debugging, Connect IQ has a unit testing framework called Run No Evil, and a debugger that's included in the Connect IQ plug-in for Eclipse that can be used to dig into potential issues within the Connect IQ simulator. Check out the Debugging and Unit Testing chapters of the Core Topics Guide for more info.

In addition to these tools, there are two general types of on-device crash that can occur related to Connect IQ, which each generate log files: app crashes and device crashes.

App crashes typically result in an app quitting unexpectedly or displaying an 'IQ!' icon, but does not cause the entire device to crash or reboot. This kind of crash is most commonly due to a bug in an app, though it can also be due to a bug in Connect IQ itself. Whenever an app crash occurs, a /GARMIN/APPS/LOGS/CIQ_LOG.YML file is written to the device, which usually contains a call stack from the app (older devices may write a CIQ_LOG.TXT file).

Device crashes typically cause the device to reboot or freeze. These indicate a Connect IQ or device firmware bug, and should be much less common than app crashes. When a device crash occurs, an ERR_LOG.TXT file is typically written to /GARMIN or /GARMIN/DEBUG on the device, containing stack trace information related to the crash. Garmin's device teams can take a look at the device crash logs to determine the cause of the crash and will typically provide a fix in a future firmware release.

When any crash log file exceeds 5 KB, it will automatically be archived to <LOGNAME>.BAK, and a new log will be started. Any old .BAK files will be overwritten when the archive occurs, so the maximum practical space available for logging is ~10 KB.

I think that I've found a bug with CIQ. How do I report it?

If you think you've found a Connect IQ bug, please report it in the Connect IQ Bug Reports tool! Please make sure to read the Bug Reporting FAQ to ensure you provide us with the information we need to investigate the problem. Be advised that if you post about a bug in the discussion forum, your thread may be moved or deleted.

Tags: Getting Started, New Developer, CIQ, Connect IQ, New

New Developer FAQ

Brandon.ConnectIQ — Mon, 03 Mar 2025 15:50:15 GMT

Revision 20 posted to Wiki by Brandon.ConnectIQ on 3/3/2025 3:50:15 PM

Where can I download the SDK?
How do I get started with Connect IQ?
I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?
Am I allowed to charge for my app though the Connect IQ app store?
Can I display seconds on my watch face?
How do I format output padded with leading zeros?
How can I load the apps I develop to my device for testing purposes?
I have side-loaded an app as described above, but app settings won't work. Why is this?
My app uses app settings, and it sometimes crashes after changing the settings, but the rest of the time it works fine. What can cause this?
I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?
How can I test or debug Connect IQ apps I am developing?
I think that I've found a bug with CIQ. How do I report it?
My app is receiving inappropriate reviews. Is there something I can do about that?

Where can I download the SDK?

The latest version of the SDK can be found at http://developer.garmin.com/connect-iq/sdk/.

How do I get started with Connect IQ?

The Connect IQ Basics Guide is a good place to start gaining familiarity with Monkey C and Connect IQ.
Once you're set up, take a look at the Core Topics and User Experience Guide for more in-depth info.
API Documentation and more Monkey C specifics are also available on our developer site.
The SDK includes a set of sample apps in the 'samples' folder that demonstrate some of the basic capabilities of Connect IQ.

I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?

Minimum SDK Selected	Eligible Target Devices	What Gets Built
3.0.x	A	3.0.x PRG for A
2.4.x	A, B	3.0.x PRG for A, 2.4.x PRG for B
1.2.x	A, B, C	3.0.x PRG for A, 2.4.x PRG for B, 1.2.x PRG for C

Am I allowed to charge for my app though the Connect IQ app store?

Can I display seconds on my watch face?

You can find out more about low power mode, full power mode, and Always On watch faces in the Connect IQ Basics Guide, or read about the related APIs in the API Docs.

How do I format output padded with leading zeros?

How can I load the apps I develop to my device for testing purposes?

In Visual Studio Code, choose View > Command Palette...
Select Monkey C: Build for Device
Select the target product from the device list
Choose an output location for the build
Select either Debug or Release depending on your intent (either will build a PRG that will run on a device)
Connect your device to the computer via USB (it should appear as a drive)
Copy the PRG file from the output location to /GARMIN/APPS on your device
Disconnect your device; the app should be available for use

I have side-loaded an app as described above, but app settings won't work. Why is this?

function readKeyInt(myApp,key,thisDefault) {
    var value = myApp.getProperty(key);
    if(value == null || !(value instanceof Number)) {
        if(value != null) {
            value = value.toNumber();
        } else {
            value = thisDefault;
        }
    }
    return value;
}

I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?

Missing state arguments for the onStart() and onStop() methods. These are currently unused arguments and were passed implicitly in earlier versions of Connect IQ, but must now be included explicitly.
An initialize() method that takes an array of options but to which none are passed.

How can I test or debug Connect IQ apps I am developing?

In addition to these tools, there are two general types of on-device crash that can occur related to Connect IQ, which each generate log files: app crashes and device crashes.

My app is receiving inappropriate reviews. Is there something I can do about that?

Developers may flag reviews of their own apps they believe are inappropriate and provide a reason explaining why. Store admins will evaluate each case and remove reviews that violate Garmin's Terms of Use (see https://www.garmin.com/en-US/legal/terms-of-use/).

Tags: Getting Started, New Developer, CIQ, Connect IQ, New

New Developer FAQ

Brandon.ConnectIQ — Mon, 03 Mar 2025 15:33:33 GMT

Revision 19 posted to Wiki by Brandon.ConnectIQ on 3/3/2025 3:33:33 PM

Where can I download the SDK?
How do I get started with Connect IQ?
I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?
Am I allowed to charge for my app though the Connect IQ app store?
Can I display seconds on my watch face?
How do I format output padded with leading zeros?
How can I load the apps I develop to my device for testing purposes?
I have side-loaded an app as described above, but app settings won't work. Why is this?
My app uses app settings, and it sometimes crashes after changing the settings, but the rest of the time it works fine. What can cause this?
I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?
How can I test or debug Connect IQ apps I am developing?
I think that I've found a bug with CIQ. How do I report it?
My app is receiving inappropriate reviews. Is there something I can do about that?

Where can I download the SDK?

The latest version of the SDK can be found at http://developer.garmin.com/connect-iq/sdk/.

How do I get started with Connect IQ?

The Connect IQ Basics Guide is a good place to start gaining familiarity with Monkey C and Connect IQ.
Once you're set up, take a look at the Core Topics and User Experience Guide for more in-depth info.
API Documentation and more Monkey C specifics are also available on our developer site.
The SDK includes a set of sample apps in the 'samples' folder that demonstrate some of the basic capabilities of Connect IQ.

I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?

Minimum SDK Selected	Eligible Target Devices	What Gets Built
3.0.x	A	3.0.x PRG for A
2.4.x	A, B	3.0.x PRG for A, 2.4.x PRG for B
1.2.x	A, B, C	3.0.x PRG for A, 2.4.x PRG for B, 1.2.x PRG for C

Am I allowed to charge for my app though the Connect IQ app store?

Can I display seconds on my watch face?

You can find out more about low power mode, full power mode, and Always On watch faces in the Connect IQ Basics Guide, or read about the related APIs in the API Docs.

How do I format output padded with leading zeros?

How can I load the apps I develop to my device for testing purposes?

In Eclipse, choose Connect IQ > Build for Device Wizard…
In the Build for Device Wizard window:
- Choose the project you wish to build
- Choose the target device
- Choose the SDK version to target
- Specify a signing key
- Set an output location
- Click Finish
Connect your device to the computer via USB (it should appear as a drive)
Copy the PRG file made by the Build for Device Wizard from the output location to /GARMIN/APPS on your device
Disconnect your device; the app should be available for use

I have side-loaded an app as described above, but app settings won't work. Why is this?

function readKeyInt(myApp,key,thisDefault) {
    var value = myApp.getProperty(key);
    if(value == null || !(value instanceof Number)) {
        if(value != null) {
            value = value.toNumber();
        } else {
            value = thisDefault;
        }
    }
    return value;
}

I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?

Missing state arguments for the onStart() and onStop() methods. These are currently unused arguments and were passed implicitly in earlier versions of Connect IQ, but must now be included explicitly.
An initialize() method that takes an array of options but to which none are passed.

How can I test or debug Connect IQ apps I am developing?

In addition to these tools, there are two general types of on-device crash that can occur related to Connect IQ, which each generate log files: app crashes and device crashes.

My app is receiving inappropriate reviews. Is there something I can do about that?

Tags: Getting Started, New Developer, CIQ, Connect IQ, New

Getting Started with Connect IQ BLE Development

Ashley.Garmin — Tue, 15 Oct 2024 17:02:07 GMT

Current Revision posted to Wiki by Ashley.Garmin on 10/15/2024 5:02:07 PM

Starting with Connect IQ version 3.1.0, developers have the ability to communicate directly with devices via the Bluetooth Low Energy wireless communication protocol. This has opened up a whole new world of possibilities for what can be done with Connect IQ. For the uninitiated, the setup process to get started can seem quite daunting. The purpose of this setup guide is to help lighten the load to get developers off the ground as quickly as possible.

Resources

When going through this guide, developers will want to keep a few things handy.

Connect IQ BLE API Documentation - Having the API Documentation close by will be critical (especially in the later steps of this document).
Nordic nRF52 DK - The Connect IQ team has built out the Connect IQ SDK tools to be compatible with the Nordic nRF52 DK Bluetooth 5 and Bluetooth mesh Development Kit for nRF52810.
Nordic Documentation Page - The Nordic Documentation has links to all of the resources needed to use the nRF52 DK.

nRF Connect For Desktop - The nRF Connect For Desktop application allows developers to flash new firmware to the board, monitor connections, etc. This software is necessary to program the board to work correctly with the Connect IQ simulator.
An up-to-date Connect IQ SDK - To use the BLE APIs, developers should be working with the current version of the Connect IQ SDK.
Firmware for the nRF52 DK or nRF52840 Dongle - The memory layout of the development board will need to be flashed to a different firmware for use with the Connect IQ SDK: nRF52 DK firmware or nRF52840 Dongle firmware

Windows

The drivers and applications needed to communicate with the nRF52 DK are all included in the installation of nRF Connect for Desktop for the Windows platform. Once this application is installed along with the necessary drivers, the nRF52 DK should be found by the nRF Connect for Desktop application.

At this point, proceed to the Using Nordic nRF Connect section.

Mac

When using macOS, developers will need to manually install the JLink/JTrace USB drivers to communicate with the nRF52 DK board. To do so, download and install the Segger JLink installer package 6.22g for Mac.

Once this is completed, developers will need to install the nRF Connect for Desktop for Mac.

At this point, proceed to the Using Nordic nRF Connect section.

Linux

When using Linux, developers will need to manually install the JLink/JTrace USB drivers to communicate with the nRF52 DK board. To do so, download and install using the appropriate Segger JLink installer for Linux:

32-bit: JLink_6.22g - 32
64-bit: JLink_6.22g - 64

Once this is completed developers will need to install the nRF Connect for Desktop for Linux.

At this point, proceed to the Using Nordic nRF Connect section.

Using Nordic nRF Connect

The nRF Connect Desktop application will need to be installed. Please see the above sections for the appropriate links.

Once installed, launch the application. Click Add/remove apps
Install the Programmer app.
Plug in the nRF52 board.
Launch the Programmer app.
Near the top left, click Select device.
Select the correct device.
Click Read to see the Memory Layout of the connected device.[12]
Drag and drop or click Add HEX file to prepare the desired Memory Layout with the proper .hex file.
Click Erase & write to flash the new memory layout.

Finding The COM Port

Now that the board is properly communicating with the computer, it’s time to figure out which port it’s utilizing.

Windows

Open up Device Manager and find your device under Ports.

It will look something like this:

The communications port is listed in parentheses. In the example above the communications port is COM4. Copy this to be used in a later step and proceed to Setting the COM Port.

Mac

Open up a terminal and type:

ls /dev/tty.usbmodem*

then press Tab. This should list out the port information in the format /dev/tty.usbmodem<number>. Copy this to be used in a later step and proceed to Setting the COM Port.

Linux

Open up a terminal and type:

ls /dev/ttyACM*

then press Tab. This should list out the port information in the format /dev/ttyACM<number>. Copy this to be used in a later step and proceed to Setting the COM Port.

Setting the COM Port

At this point the nRF52 is properly communicating with the development environment and the com port information has been retrieved. The final step is to set the COM port in the Connect IQ Simulator.

Launch the simulator via Eclipse or command line tools.
Select Settings > BLE Settings
In the dialog box, enter the COM port information from Finding the COM Port.
Click OK.

It’s possible that developers might encounter an error. This is likely due to a failure to set the COM Port for the Connect IQ simulator. If an error occurs, then developers have a few things they can check.

Double check the COM Port assignment: Follow the steps for the correct environment to find and confirm the COM Port.
Ensure there are no copy/paste errors: Double check the information entered when setting the COM Port.

That’s it! If all goes well, then the Connect IQ Simulator will use the nRF52 DK board BLE chipset to communicate with nearby BLE devices per the Connect IQ Bluetooth Low Energy APIs. For more information on the APIs, please refer to the API documentation and sample applications included in the Connect IQ SDK.

Tags: BLE, Getting Started, CIQ, FAQ

App Approval Exceptions

Brandon.ConnectIQ — Wed, 15 May 2024 18:01:43 GMT

Current Revision posted to Wiki by Brandon.ConnectIQ on 5/15/2024 6:01:43 PM

Garmin is as permissive as possible when approving apps for inclusion on the Connect IQ app store. Aside from apps that contain offensive material or are subject to DMCA take-down requests, we're happy to allow most everything else that our app developers would like to share with the Garmin community unless it falls under one of the following exceptions:

Extreme Sports

Apps designed for scuba diving, free diving, skydiving, base-jumping, and extreme flight sports will not be listed on the app store for the following reasons:

The diving features available on Descent products are the only Garmin features intended for underwater diving use.
The altimeter/barometer feature available in some Garmin devices is intended to be used for general altitude reference only, and is not intended to be used for extreme sports such as skydiving, base-jumping or other activities that require the use of equipment that is designed and intended for such use. The Jumpmaster feature on Garmin tactix products is intended to be used for skydiving activities by experienced skydivers. This is the only Garmin feature that is intended for use while skydiving.

Aviation

Aviation-specific apps (excluding aviation-themed Watch Faces) must include the following disclaimer at the top of their app description:

WARNING: The app is intended only as an in-flight aid and should not be used as a primary information source. If the app contains a barometric altimeter, it will not function in a pressurized aircraft and should not be used in a pressurized aircraft.

Safety Awareness

Apps designed for safety awareness purposes, such as incident detection or use with a Varia radar, may not be listed in the interest of customer safety.

Medical

Apps designed for medical use may be subject to regulation by the U.S. Food and Drug Administration (FDA) as a device such that it needs clearance or approval by the agency before it can be lawfully marketed in the United States. The FDA has issued two guidance documents on the topic:

Mobile Medical App Guidance, https://www.fda.gov/media/80958/download
Clinical Decision Support Guidance, https://www.fda.gov/media/109618/download

Apps subject to these guidelines may be required to include appropriate documentation. Otherwise, the app description must be updated to reflect that the app is not intended to be used for the purposes of medical treatment and is intended for educational purposes only.

Garmin designs and tests its products for their intended use to ensure safe operation and a positive customer experience. If you have developed or are currently developing apps subject to these guidelines, we apologize and do not want to be a source of discouragement. You may still continue to build and distribute these apps as you wish outside of the Connect IQ app store, but we cannot allow content of this nature to be placed on any Garmin affiliated app resource.

Chinese National Flag

Chinese law describes the contexts within which the Chinese national flag may and may not be used. Article 20 of the Law of the PRC on the National Flag (http://www.lawinfochina.com/display.aspx?id=34075&lib=law) states that the national flag and the design shall not be used in product appearance, for commercial use, or for trademark and patent licensing purposes., which means it cannot be included in Connect IQ apps for display on Garmin products.

Garmin Branding

Apps that use Garmin branding must comply with Garmin's Consumer Brand Style Guide, which includes specifications for things like logo colors, typeface, and positioning.

Tags: awareness, Free Diving, Base-Jumping, Scuba, extreme sports, Approval, Extreme Flight, App Rejected, Diving, medical apps, Approval Exceptions, safety

App Approval Exceptions

Brandon.ConnectIQ — Wed, 15 May 2024 17:58:18 GMT

Revision 9 posted to Wiki by Brandon.ConnectIQ on 5/15/2024 5:58:18 PM

Extreme Sports

Apps designed for scuba diving, free diving, skydiving, base-jumping, and extreme flight sports will not be listed on the app store for the following reasons:

The diving features available on Descent products are the only Garmin features intended for underwater diving use.
The altimeter/barometer feature available in some Garmin devices is intended to be used for general altitude reference only, and is not intended to be used for extreme sports such as skydiving, base-jumping or other activities that require the use of equipment that is designed and intended for such use. The Jumpmaster feature on Garmin tactix products is intended to be used for skydiving activities by experienced skydivers. This is the only Garmin feature that is intended for use while skydiving.

Aviation

Aviation-specific apps (excluding aviation-themed Watch Faces) must include the following disclaimer at the top of their app description:

Safety Awareness

Apps designed for safety awareness purposes, such as incident detection or use with a Varia radar, may not be listed in the interest of customer safety.

Medical

Mobile Medical App Guidance, https://www.fda.gov/media/80958/download
Clinical Decision Support Guidance, https://www.fda.gov/media/109618/download

Chinese National Flag

Chinese law describes the contexts within which the Chinese national flag may and may not be used. Article 20 of the Law of the PRC on the National Flag (http://www.lawinfochina.com/display.aspx?id=34075&lib=law) states that the national flag and the design shall not be used as product appearance or commercial for trademark or patent licensing purpose, which means it cannot be included in Connect IQ apps for display on Garmin products.

Garmin Branding

Apps that use Garmin branding must comply with Garmin's Consumer Brand Style Guide, which includes specifications for things like logo colors, typeface, and positioning.

Tags: awareness, Free Diving, Base-Jumping, Scuba, extreme sports, Approval, Extreme Flight, App Rejected, Diving, medical apps, Approval Exceptions, safety

New Developer FAQ

Brandon.ConnectIQ — Tue, 16 Apr 2024 21:51:16 GMT

Revision 18 posted to Wiki by Brandon.ConnectIQ on 4/16/2024 9:51:16 PM

Where can I download the SDK?
How do I get started with Connect IQ?
I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?
Am I allowed to charge for my app though the Connect IQ app store?
Can I display seconds on my watch face?
How do I format output padded with leading zeros?
How can I load the apps I develop to my device for testing purposes?
I have side-loaded an app as described above, but app settings won't work. Why is this?
My app uses app settings, and it sometimes crashes after changing the settings, but the rest of the time it works fine. What can cause this?
I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?
How can I test or debug Connect IQ apps I am developing?
I think that I've found a bug with CIQ. How do I report it?
My app is receiving inappropriate reviews. Is there something I can do about that?

Where can I download the SDK?

The latest version of the SDK can be found at http://developer.garmin.com/connect-iq/sdk/.

How do I get started with Connect IQ?

The Connect IQ Basics Guide is a good place to start gaining familiarity with Monkey C and Connect IQ.
Once you're set up, take a look at the Core Topics and User Experience Guide for more in-depth info.
API Documentation and more Monkey C specifics are also available on our developer site.
The SDK includes a set of sample apps in the 'samples' folder that demonstrate some of the basic capabilities of Connect IQ.

I just downloaded the latest SDK. Can I build apps that will work on any device that supports Connect IQ?

Minimum SDK Selected	Eligible Target Devices	What Gets Built
3.0.x	A	3.0.x PRG for A
2.4.x	A, B	3.0.x PRG for A, 2.4.x PRG for B
1.2.x	A, B, C	3.0.x PRG for A, 2.4.x PRG for B, 1.2.x PRG for C

Am I allowed to charge for my app though the Connect IQ app store?

Yes, you are! It is acceptable to list prices, link to payment sites, or ask for donations on the Connect IQ app store as long as solicitations are related to your app. The app store falls under the the Connect IQ SDK License Agreement, which does not forbid solicitation for sales of apps by app developers. However, solicitation for business on Garmin sites other than the app store (such as this forum) is prohibited but Garmin's Terms of Use.

Can I display seconds on my watch face?

You can find out more about low power mode, full power mode, and Always On watch faces in the Connect IQ Basics Guide, or read about the related APIs in the API Docs.

How do I format output padded with leading zeros?

How can I load the apps I develop to my device for testing purposes?

In Eclipse, choose Connect IQ > Build for Device Wizard…
In the Build for Device Wizard window:
- Choose the project you wish to build
- Choose the target device
- Choose the SDK version to target
- Specify a signing key
- Set an output location
- Click Finish
Connect your device to the computer via USB (it should appear as a drive)
Copy the PRG file made by the Build for Device Wizard from the output location to /GARMIN/APPS on your device
Disconnect your device; the app should be available for use

I have side-loaded an app as described above, but app settings won't work. Why is this?

function readKeyInt(myApp,key,thisDefault) {
    var value = myApp.getProperty(key);
    if(value == null || !(value instanceof Number)) {
        if(value != null) {
            value = value.toNumber();
        } else {
            value = thisDefault;
        }
    }
    return value;
}

I keep getting a "Too Many Arguments Error", but I never used to get this. What is going on?

Missing state arguments for the onStart() and onStop() methods. These are currently unused arguments and were passed implicitly in earlier versions of Connect IQ, but must now be included explicitly.
An initialize() method that takes an array of options but to which none are passed.

How can I test or debug Connect IQ apps I am developing?

In addition to these tools, there are two general types of on-device crash that can occur related to Connect IQ, which each generate log files: app crashes and device crashes.

My app is receiving inappropriate reviews. Is there something I can do about that?

Tags: Getting Started, New Developer, CIQ, Connect IQ, New

App Approval Exceptions

Brandon.ConnectIQ — Fri, 01 Mar 2024 19:18:14 GMT

Revision 8 posted to Wiki by Brandon.ConnectIQ on 3/1/2024 7:18:14 PM

Extreme Sports

Apps designed for scuba diving, free diving, skydiving, base-jumping, and extreme flight sports will not be listed on the app store for the following reasons:

The diving features available on Descent products are the only Garmin features intended for underwater diving use.
The altimeter/barometer feature available in some Garmin devices is intended to be used for general altitude reference only, and is not intended to be used for extreme sports such as skydiving, base-jumping or other activities that require the use of equipment that is designed and intended for such use. The Jumpmaster feature on Garmin tactix products is intended to be used for skydiving activities by experienced skydivers. This is the only Garmin feature that is intended for use while skydiving.

In addition, aviation-specific apps (excluding aviation-themed Watch Faces) must include the following disclaimer at the top of their app description:

Safety Awareness

Apps designed for safety awareness purposes, such as incident detection or use with a Varia radar, may not be listed in the interest of customer safety.

Medical

Mobile Medical App Guidance, https://www.fda.gov/media/80958/download
Clinical Decision Support Guidance, https://www.fda.gov/media/109618/download

Tags: awareness, Free Diving, Base-Jumping, Scuba, extreme sports, Approval, Extreme Flight, App Rejected, Diving, medical apps, Approval Exceptions, safety

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.

Tips and Tricks FAQ

Brandon.ConnectIQ — Tue, 12 Dec 2023 20:43:42 GMT

Current Revision posted to Wiki by Brandon.ConnectIQ on 12/12/2023 8:43:42 PM

This is a place where we're throw any interesting threads that contain development tips, tricks, and recommendations.

Python tool for translating XML strings: https://forums.garmin.com/developer/connect-iq/f/discussion/292146/translate-strings-xml---python-code-and-web-tool
Tips for optimizing Monkey C Code: https://forums.garmin.com/developer/connect-iq/f/discussion/291568/optimizing-monkey-c-code
Prettier VS Code Extension: https://forums.garmin.com/developer/connect-iq/f/discussion/294852/big-update-to-prettier-extension-monkeyc
Using GitHub Actions and Docker to test apps: https://forums.garmin.com/developer/connect-iq/f/discussion/303170/connectiq-docker-image-and-github-action
Decoding PC line numbers in Connect IQ call stacks: https://forums.garmin.com/developer/connect-iq/f/discussion/231129/so-you-have-a-ciq_log-file-but-all-you-see-is-pc-without-a-friendly-stack-trace---what-to-do

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.

Tips and Tricks FAQ

Brandon.ConnectIQ — Fri, 29 Jul 2022 13:43:57 GMT

Revision 4 posted to Wiki by Brandon.ConnectIQ on 7/29/2022 1:43:57 PM

This is a place where we're throw any interesting threads that contain development tips, tricks, and recommendations.

Python tool for translating XML strings: https://forums.garmin.com/developer/connect-iq/f/discussion/292146/translate-strings-xml---python-code-and-web-tool
Tips for optimizing Monkey C Code: https://forums.garmin.com/developer/connect-iq/f/discussion/291568/optimizing-monkey-c-code
Prettier VS Code Extension: https://forums.garmin.com/developer/connect-iq/f/discussion/294852/big-update-to-prettier-extension-monkeyc
Using GitHub Actions and Docker to test apps: https://forums.garmin.com/developer/connect-iq/f/discussion/303170/connectiq-docker-image-and-github-action

Tips and Tricks FAQ

Brandon.ConnectIQ — Fri, 29 Jul 2022 13:43:37 GMT

Revision 3 posted to Wiki by Brandon.ConnectIQ on 7/29/2022 1:43:37 PM

This is a place where we're throw any interesting threads that contain development tips, tricks, and recommendations.

Python tool for translating XML strings: https://forums.garmin.com/developer/connect-iq/f/discussion/292146/translate-strings-xml---python-code-and-web-tool
Tips for optimizing Monkey C Code: https://forums.garmin.com/developer/connect-iq/f/discussion/291568/optimizing-monkey-c-code
Prettier VS Code Extension: https://forums.garmin.com/developer/connect-iq/f/discussion/294852/big-update-to-prettier-extension-monkeyc
Using GitHub Actions and Docker to test apps: https://forums.garmin.com/developer/connect-iq/f/discussion/303170/connectiq-docker-image-and-github-action

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.

Tips and Tricks FAQ

Brandon.ConnectIQ — Mon, 23 May 2022 15:45:43 GMT

Revision 2 posted to Wiki by Brandon.ConnectIQ on 5/23/2022 3:45:43 PM

This is a place where we're throw any interesting threads that contain development tips, tricks, and recommendations.

Python tool for translating XML strings: https://forums.garmin.com/developer/connect-iq/f/discussion/292146/translate-strings-xml---python-code-and-web-tool
Tips for optimizing Monkey C Code: https://forums.garmin.com/developer/connect-iq/f/discussion/291568/optimizing-monkey-c-code
Prettier VS Code Extension: https://forums.garmin.com/developer/connect-iq/f/discussion/294852/big-update-to-prettier-extension-monkeyc

Tips and Tricks FAQ

Brandon.ConnectIQ — Fri, 29 Apr 2022 15:47:09 GMT

Revision 1 posted to Wiki by Brandon.ConnectIQ on 4/29/2022 3:47:09 PM

This is a place where we're throw any interesting threads that contain development tips, tricks, and recommendations.

Python tool for translating XML strings: https://forums.garmin.com/developer/connect-iq/f/discussion/292146/translate-strings-xml---python-code-and-web-tool
Tips for optimizing Monkey C Code: https://forums.garmin.com/developer/connect-iq/f/discussion/291568/optimizing-monkey-c-code

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.