Connect IQ Bug Reports

If a developer has multiple apps or a suite of apps, it would be interesting if there could be shared storage. For example, a widget could read from data written by a related app to display summary info, last activity info, etc. This is a somewhat...

Using modified Comm samples from the CIQ SDK and the CIQ Android Mobile SDK, any attempt at communication from the phone to the Garmin device results in FAILURE_DURING_TRANSFER, while messages go through normally in the other direction. Also see https...

The settings won’t let me put a semicolon between the minutes and the seconds for the pace setter.

Seems that as a result a recent firmware update to the vivoactive 3 the Sys.getDeviceSettings().phoneConnected as well as settings.connectionInfo[:bluetooth].state always return true/CONNECTION_STATE_CONNECTED regardless if the phone is connected or...

Hi, not only that CIQ 3.0 implementation of MapView and MapTrackView still have more issues than actual working features, CIQ 3.1 even made them worse. Newly, UI rendered by both classes can not be refreshed on CIQ 3.1 devices by calls from code...

I can't use the simulator and thus connectiq on Fedora 30. I assume all modern distros are affected because libwebkitgtk-1.0.so.0 is way too old to be included or even available on current generation distributions. Please update your deps or better...

jim_m_58 Suggested a way to toggle whether app settings are saved between app runs. Currently, app settings are at least cleared between runs every time the target device is changed, which can make testing cumbersome. Original post: i can't save app...

Under certain circumstances, ActivityInfo::distanceToDestination seems to have the same value as distanceToNextPoint, instead of reflecting the distance to the end of the course, as expected. Hopefully I am not misinterpreting what distanceToDestination...

Hello, recently (after some firmware or Connect app update?) I started getting BLE_REQUEST_TOO_LARGE (code -102) as a response to my makeWebRequest (it's a request from watchface's background service). The server doesn't even register this request...

Please check the newest firmware for issues that causes watch faces to crash. e.g. https://apps.garmin.com/de-DE/apps/fc3f9b9f-add6-46cb-8e0b-9a2172a04c31 All vivoactive 3 users with the latest firmware are reporting the same affect, the watch face...