Connect IQ App Development Discussion - Recent Threads

RE: Feature Request: Updated Simulator

jim_m_58 — Fri, 12 Jun 2026 12:24:21 GMT

Automating updates has been requested a number of times since 2015, when I started doing CIQ apps. It's a bit more complex than may first appear, when it comes to things like version numbers. "what's new", pictures, etc.. Setting up the automation each time would likely take as long, or longer, than the current process. You'll also find that once an app is stable, you really don't update that often - maybe once in a while to add a new device.

Automation also means catching/handling any possible error. Things you'll see if doing it manually. Sometimes the app store is down for example, or there are network issues.

Using beta apps is also handy if you test on more than one device. Update the store, and the app is available on all your devices. I have a number of devices I regularly test with, for example.

Feature Request: Updated Simulator

andrewM — Tue, 09 Jun 2026 11:26:36 GMT

We are living in 2026 right now, where we can do a lot of things programmatically. Garmin Simulator is quite behind and actually my biggest pain in development cycle.
I have time measured my bug fixing today. Out of 4 hours spent on development, 3.5 hours was spent to connecting the real watch back and forth to make sure my app actually works properly. (in simulator it always works).

The simulator just need a few tweaks to be WAY better:

1. Service or MCP to interact with simulator programmatically.

I want to automate tests, that actually do taps or button interactions, to do a lot of UI work. It is repetitive and time consuming to do by hand, and not everything can be covered via standard test suite. I want to make screenshots programmatically so i can know which tests have failed and where.

2. I want more options to run simulator from command line: I have an app that works with accelerometer and gyro and it needs a playback FIT file. I have to manually select it every time i run simulator. It is time consuming and distracting. Let me just run a simulator with a playable FIT file attached. With pre-selected languages. With pre-selected other parameters.

3. i want to see in simulator real device limitations. I have faced multiple times the app runs smoothly on simulator but it runs out of memory on older real hardware.

4. That's a nice bonus, but i want to be able to connect to a real Garmin device from the debugger wirelessly. Taking watch on and off constantly connecting to a computer back and forth to test the motion-related stuff is exhausting. I know it's not for every developer, but we are not only producing millions of watch faces.

5. I won't even mention BLE .requestBond() that is absent from simulator for quite a while now. BLE development is more than a pain.

C'mon, Garmin, you can do better! Or, open source simulator so we can code extra plugins ourselves.

RE: Feature Request: Updated Simulator

andrewM — Fri, 12 Jun 2026 06:39:51 GMT

Yeah, it still doesn't fix manual uploads and reinstalls huge time overhead, does it? Or is there a way to automate this process?

BLE problem

jeromej_ — Thu, 11 Jun 2026 09:00:34 GMT

Hello Gall,

Chatgpt and I need help...

I am developing a Connect IQ / Monkey C application on a Garmin fēnix 7.

The application connects directly to a GoPro using Bluetooth Low Energy. The GoPro exposes the Open GoPro BLE service:

Service UUID: 0000fea6-0000-1000-8000-00805f9b34fb
Query Write characteristic: b5f90076-aa8d-11e3-9046-0002a5d5c51b
Query Response characteristic: b5f90077-aa8d-11e3-9046-0002a5d5c51b

The application can successfully:

scan and find the GoPro,
connect using BluetoothLowEnergy.pairDevice(scanResult),
discover the FEA6 service,
find GP-0076 and GP-0077,
enable notifications on GP-0077,
write to GP-0076 using WRITE_TYPE_WITH_RESPONSE.

However, the write to GP-0076 fails with status 18, which appears to mean insufficient authentication. The Garmin device also shows that the app is using an “OPEN connection”, described as not encrypted and not authenticated.

This seems to be the root problem: the GoPro requires an authenticated/encrypted BLE connection for this characteristic, but the Connect IQ app only gets an open connection.

I tried the documented bonding/security options:

BluetoothLowEnergy.setConnectionStrategy(BluetoothLowEnergy.CONNECTION_STRATEGY_SECURE_PAIR_BOND)

When called before scanning/pairing, the application crashes before the Garmin BLE permission prompt appears.

Crash details:

Device: fēnix 7
Part Number: 006-B3906-00
Firmware Version: 26.09
Connect IQ Version: 6.0.2
Error: System Error
Details: Failed invoking <symbol>
Time: 2026-06-11T08:04:50Z
Stack:
- pc: 0x1000191e
- pc: 0x10002360
- pc: 0x10003a21

Device.requestBond()

When called after the BLE connection is established, the app remains stuck waiting. onEncryptionStatus() is not called, and the GoPro does not become usable as an authenticated BLE peripheral.

The result is:

default/open connection works but GP-0076 write fails with authentication error 18;
requestBond() does not complete;
setConnectionStrategy(CONNECTION_STRATEGY_SECURE_PAIR_BOND) crashes the app on the fēnix 7.

Could you please confirm:

Is BluetoothLowEnergy.setConnectionStrategy() supported on fēnix 7 with firmware 26.09 / Connect IQ 6.0.2?
If not, what is the supported way for a Connect IQ app on fēnix 7 to establish an encrypted/authenticated BLE connection to a peripheral?
Is Device.requestBond() expected to trigger onEncryptionStatus() on fēnix 7?
Is there any current limitation preventing Connect IQ apps from using authenticated GATT characteristics on fēnix 7?

This looks less like a GoPro protocol issue and more like a Connect IQ BLE security/bonding issue, because the app reaches the characteristic correctly and the failure occurs at the GATT authentication level.

Thank you,
Jerome

SDK Bug: The currently running app requires a newer SDK to run. Please select a newer SDK in the Connect IQ SDK Manager.

pstoppani — Tue, 09 Jun 2026 14:46:31 GMT

I ran the SDK Manager and it update many devices but no new SDK. Now when I try to run something in the sim I get a popup saying "

The currently running app requires a newer SDK to run. Please select a newer SDK in the Connect IQ SDK Manager."

Garmin, this is a showstopper bug. PLEASE fix ASAP.

Thx,

Pete

RE: SDK Bug: The currently running app requires a newer SDK to run. Please select a newer SDK in the Connect IQ SDK Manager.

Brandon.ConnectIQ — Wed, 10 Jun 2026 20:04:48 GMT

Which device(s) were you attempting to run when you encountered this issue? Did this happen on any device?

RE: Calendar on Watch Face

beva — Wed, 10 Jun 2026 18:22:57 GMT

Currently there is a complication with the next calendar event from the native calendar glance.

Calendar on Watch Face

Former Member — Thu, 06 Feb 2020 02:42:59 GMT

Hi all!

By hobby, I am a software developer and I recently purchased a Fenix 6. I've been looking into making a watch face that better fits my needs and I have stumbled upon a problem.
Is there no way currently to have a watch face display the next calendar event? When I scroll down on my watch, there is a calendar widget that does exactly that! I have googled all over and visited forms from 4 years ago that said it was not possible. If that still the case? How does the widget have access to the next calendar event and how do I implement that on to a watch face?

Thanks in advance.

RE: Feature Request: Updated Simulator

jim_m_58 — Wed, 10 Jun 2026 11:32:12 GMT

With beta versions, you, and only you can see and install the app from the store. And unlike sideloads, you can test out app settings and fitcontrib/user data. And depending on what you are looking at, you can use println calls to help with debugging.

Core Topics

Just one of the tricks you learn with experience.

RE: Feature Request: Updated Simulator

andrewM — Wed, 10 Jun 2026 11:14:06 GMT

Tim:

No, actually. When you test something complex, you want to develop/test/iterate as fast as possible. If you build-upload (manually btw, there is no automation there as well), then wait till it rolls out, get some 1-star ratings in between because something is broken and users are impatient, it doesn't work, no matter you out "beta" there or not. You don't have a lot of debug info from store builds as well, unless you code some built in complicated debug/log harness that actually eats tons of memory and battery on the watch, leading to a very poor performance of the app.

RE: Feature Request: Updated Simulator

Tim — Wed, 10 Jun 2026 10:10:44 GMT

I was about to say #4 gets my up vote but isn't that the point of Beta versions on the store? Apologies if i'm missing something

RE: Garmin Connect Developer Program - Access Request Rejected Without Notification

8800604 — Wed, 10 Jun 2026 07:35:50 GMT

It would definitely help if Garmin provided clearer rejection reasons and status updates during the application process.

@fnf

Garmin Connect Developer Program - Access Request Rejected Without Notification

leonjasonherbert — Fri, 10 Apr 2026 16:09:56 GMT

Hi everyone,

I'm hoping someone from the Garmin team or the community can help point me in the right direction.

I submitted a Garmin Connect Developer Program access request on March 1 (Ticket 200767) for my company, So Smart Apps LLC. We're building a health and wellness app called Apex Life that integrates wearable data for AI-powered life coaching. Garmin integration is our top priority.

Timeline:

March 1: Submitted the access request
March 2: Marc Lussi from Garmin Connect Partner Services asked for project background - I provided a detailed response the same day
March 3: Marc asked for our website and Privacy Policy links
March 5: I provided both (sosmartapps.app and our Privacy Policy page)
March 5: Marc confirmed the request was "successfully verified" and entered the approval process (up to two business weeks)
March 23, March 31, April 4: I sent follow-up emails - no response to any of them

I recently learned through a completely separate channel that the request was apparently rejected. However, I never received any rejection notification or explanation. The last communication I received was Marc confirming the request was verified and in the approval process.

I'm not here to complain - I just want to understand what happened and how to move forward. Specifically:

Has anyone else experienced a similar situation with the Connect Developer Program?
Is there a better channel to reach the developer program team when email support goes unresponsive?
If a request is rejected, is there a way to get the specific reason and resubmit?

We provided everything that was asked of us, and our use case is straightforward - read-only access to Health API data (steps, sleep, heart rate, stress, body composition) with explicit user consent. We're a registered LLC and a legitimate business.

Any advice or guidance would be greatly appreciated.

Thanks,
Leon Herbert
Founder, So Smart Apps LLC

RE: Feature Request: Updated Simulator

Sam Dumont — Wed, 10 Jun 2026 06:19:38 GMT

WOW ! This is amazing !!!

RE: VS Code "ERROR: Unable to load devices: null" error. Any suggestions for fix?

A.Se.S — Tue, 09 Jun 2026 21:20:52 GMT

My computer is in Turkish and I fixed this exact same error by changing Java environment settings to English.

VS Code "ERROR: Unable to load devices: null" error. Any suggestions for fix?

5d4f41eda4fb46208eb0ee3e09738cf9 — Sun, 02 Jul 2023 07:27:03 GMT

Hi,

I am new to Garmin Connect IQ and this forum. I just want to create a customized watchface and wanted to give it a try. Followed the instructions on https://developer.garmin.com/connect-iq/reference-guides/visual-studio-code-extension/ and also downloaded latest version of SKD and all devices using SKDManager. Even though I have followed all the steps when I run the code the simulator does not open and I get the following error. I am sure that I have added all the devices to the code. What do you guys recommend me to check?

----------------------------------------

ERROR: Unable to load devices: null
usage: monkeyc [-a <arg>] [-b <arg>] [--build-stats <arg>] [-c <arg>] [-d <arg>]
[--debug-log-level <arg>] [--debug-log-output <arg>] [-e]
[--Eno-invalid-symbol] [-f <arg>] [-g] [-h] [-i <arg>] [-k] [-l <arg>]
[-m <arg>] [--no-gen-styles] [-o <arg>] [-O <arg>] [-p <arg>] [-r] [-s
<arg>] [-t] [-u <arg>] [-v] [-w] [-x <arg>] [-y <arg>] [-z <arg>]

........................

The terminal process "C:\Program Files (x86)\Common Files\Oracle\Java\javapath\java.exe '-Xms1g', '-Dfile.encoding=UTF-8', '-Dapple.awt.UIElement=true', '-jar', 'c:\Users\mustafa\AppData\Roaming\Garmin\ConnectIQ\Sdks\connectiq-sdk-win-6.2.1-2023-06-26-124cb49c5\bin\monkeybrains.jar', '-o', 'bin\olmadi_1.prg', '-f', 'c:\Users\mustafa\Documents\deneme1\olmadi_1\monkey.jungle', '-y', 'h:\garmin_test_1\deneme1\developer_key', '-d', 'fr255_sim', '-w'" terminated with exit code: 101.

RE: Feature Request: Updated Simulator

jim_m_58 — Tue, 09 Jun 2026 19:51:51 GMT

Looks like you need new FW for the nordic HW. In "core topics" for BLE, there is:

Firmware for the nRF52 DK

The memory layout of the nRF52 DK will need to be flashed to a different firmware for use with the Connect IQ SDK. The correct firmware for the development environment has been provided:
- nRF52 DK firmware
- nRF52840 Dongle firmware
Note: For SDKs prior to 9.2.0, use:
- nRF52 DK firmware (old)
- nRF52840 Dongle firmware (old)

RE: Feature Request: Updated Simulator

andrewM — Tue, 09 Jun 2026 19:49:13 GMT

ok, that one crossed off the list. Would love to see everything else though.

RE: Store upload fails: "There were no compatible devices found for the part numbers declared in the manifest file"

5667824 — Tue, 09 Jun 2026 19:45:52 GMT

Thanks!!
I have added back the devices, it worked

Store upload fails: "There were no compatible devices found for the part numbers declared in the manifest file"

5667824 — Thu, 04 Jun 2026 09:28:04 GMT

I'm trying to upload a new version of my watch face to the Connect IQ Store and the upload is rejected with:

There were no compatible devices found for the part numbers declared in the manifest file. {0}

The app builds and runs fine in the simulator and on a physical device. It's a type="watchface" app with minApiLevel="4.0.0".

My manifest declares 57 products, including several recent devices (e.g. fenix8pro47mm, venux1, fr970, instinct3amoled45mm, vivoactive6).

Details:

I exported the .iq using ["Export Project" / Build > Export Wizard] with all products selected.
This is an [update to an existing app / brand-new submission].

Questions:

What exactly causes this error — is it the SDK version, a specific unsupported product, or how the .iq was exported?
Is there a way to identify which part number(s) the store couldn't match?

Any guidance appreciated.

RE: Feature Request: Updated Simulator

jim_m_58 — Tue, 09 Jun 2026 19:20:45 GMT

Ok, in the 9.2.0 SDK (just released tody)

Simulator Changes

New Features

Add bonded connection support in the simulator.

RE: SDK Bug: The currently running app requires a newer SDK to run. Please select a newer SDK in the Connect IQ SDK Manager.

pstoppani — Tue, 09 Jun 2026 18:15:14 GMT

Looks like it was a timing issue. Today, SDK 9.2 became available and all is good now 🙂

RE: SDK Bug: The currently running app requires a newer SDK to run. Please select a newer SDK in the Connect IQ SDK Manager.

jim_m_58 — Tue, 09 Jun 2026 15:00:05 GMT

What SDK are you using?

RE: Feature Request: Updated Simulator

jim_m_58 — Tue, 09 Jun 2026 14:58:22 GMT

Just a guess, but it could be the nordic HW used by the sim doesn't have the ability to handle requestBond. (we are talking pre 2019) That could also be related to older Garmin devices also lacking support. For my BLE apps, I just allow an open connection and am asked when I've found a new sensor - not every time.

RE: Feature Request: Updated Simulator

Sam Dumont — Tue, 09 Jun 2026 14:33:41 GMT

If I could upvote this a million times I would do, but to be honest, I don't expect anything here. If only ONE thing could be fixed, please fix the BLE requestBond(). With the requirement of using BLE Secure for almost anything, being able to run the end to end flows in the simulator would be amazing. I am developing the (AFAIK) only GoPro remote control datafield and not having this means flying blind, baking in static data in the code to simulate the flows, etc. Very painful.

/rant on : It's feels so strange to me that Garmin is not investing more in the developer tooling : having the Connect IQ store means that it's the only viable ecosystem for tech enthusiast athletes because it's the only one where you can be sure to see support for the latest peripherals, but it feels like they are actively fighting against the people who bring that value. /rant off