Connect IQ Store Discussion - Recent Threads

Paid app: declared devices accepted at upload, then not listed. Is there a canonical monetization-supported device list?

Meridian — Wed, 19 Aug 2026 14:38:47 GMT

We publish a paid Device App. In our latest version we added 13 products at API 3.4. The upload was accepted with no warning and all products built, but the store lists only the fenix 6 Pro family. All eight MARQ (first generation) models and both Descent Mk2 models never appeared.

Every one of those is listed on the Monetization > App Sales page under "API Level 3.4". We also have D2 Air X10 (006-B4125-00) in our manifest, listed on that same page under "API Level 5.0", and it has never appeared in our listing either, well before this release.

From the "Compatible Devices bug" report I gather that store compatibility is the intersection of minimum supported CIQ, monetization support, and the app manifest, and that monetization support covers a narrower set than the App Sales page implies. That would explain what we are seeing, since the fenix 6 Pro is mentioned there as an exception among the older devices.

Two questions:

1. Is there a canonical, current list of monetization-supported devices? If the App Sales table includes devices that are not monetization enabled, it cannot be used to plan a device expansion, which is what we used it for.

2. Could the upload warn when declared products have no monetization support? At the moment it succeeds silently, and the only way to find the gap is to diff the live listing afterwards, which is a full release cycle too late. A line in the upload response naming the affected products would have saved us a release.

Part numbers, in case they are useful: 006-B3251-00 (MARQ Athlete), 006-B3258-00 (Descent Mk2), 006-B4125-00 (D2 Air X10).

Thanks.

RE: Paid app: declared devices accepted at upload, then not listed. Is there a canonical monetization-supported device list?

jim_m_58 — Thu, 03 Sep 2026 23:31:05 GMT

I'm pretty sure that the only pre-ciq 4 devices that support Garmin Monitorization are the f6 pro

That's why the older devices don't show.. If I recall, the app was rejected if devices that didn't support monitorization were included. This could be a compromise where the app isn't just rejected.

RE: Paid app: declared devices accepted at upload, then not listed. Is there a canonical monetization-supported device list?

Meridian — Thu, 03 Sep 2026 22:46:44 GMT

Thanks both.

Not a build-stage drop here: minApiLevel is 3.4.0 and Monday's release built 122 of 122 declared products, no warnings. They upload, the portal accepts them, and then some never appear on the storefront.

The local tooling also looks okay: the same codebase ships as two listings, Garmin Pay and KiezelPay, same products declared, same API level. Garmin Pay sells 98. KiezelPay sells 118. Same manifest either way, so the filtering is server side and specific to the storefront.

On the Garmin version, every CIQ 3.4 device I declared was refused on the paid listing except the fenix 6 Pro family, fr945lte included a couple of weeks ago. On Monday that listing accepted fenix 9 Pro at CIQ 6.0.3. So not a flat API cutoff, and I cannot find a published rule separating the two.

We need a canonical monetization-supported list, or a warning at upload when a declared product will be excluded. Right now the only way to find out is to publish and diff compatibleDevicePartNumbers against what you declared.

RE: Merchant Account deactivation stuck

1700685 — Thu, 03 Sep 2026 14:35:17 GMT

Same issue. It seems stuck in this state and no response from the support.

Merchant Account deactivation stuck

MosSixtieOne — Sat, 22 Aug 2026 08:06:03 GMT

My merchant account has been stuck in the deactivation phase for 3 weeks and hasn't been closed. Because of this, I can't reactivate it. Several inquiries to support have gone unanswered. Does anyone have a similar problem or a solution?

Two apps stuck in "Pending" since Aug 31 — replacement upload rejected with a misleading manifest-ID error

majlmajl — Wed, 02 Sep 2026 06:14:32 GMT

Two of my apps have been in Pending since 31 August, while two other listings from this account (same codebase) were submitted later and approved within hours — the queue entries look stuck.

Stuck:

WingFoil (private dev) — 8f4efc35-ad13-46b9-ae9d-f01f444fe05f — 0.9.3 pending over live 0.9.2
WingFoil Field (private dev) — da0c6cb5-502b-4623-81ed-54ae40a3bf84 — 0.9.3 pending over live 0.1.0

Oddity that may help diagnose: uploading a replacement version to the first app is rejected with "The app ID within the manifest file deviates from the one originally registered" — but the package's manifest id (b1ef484c77b94a69b33d18574f3bcbde) is byte-identical to the one in the 0.9.3 package the listing accepted on Aug 31.

Approved normally in the same window: e77867b5-…, 8dad33d4-…. Could the two stuck entries be re-queued? Thanks!

[mention:62093f9dda5d4e9392eb6cc9549b374c:e9ed411860ed4f2ba0265705b8793d05] [mention:612086be554d400cacfe34b4512a6682:e9ed411860ed4f2ba0265705b8793d05]

RE: Two apps stuck in "Pending" since Aug 31 — replacement upload rejected with a misleading manifest-ID error

jim_m_58 — Wed, 02 Sep 2026 13:03:00 GMT

If you mark an app as beta, it will remain pending forever. It never gets approved. You can install it, but no one else can.

When you have a beta app, it has a different AppId than the production version,

See https://developer.garmin.com/connect-iq/core-topics/beta-apps/

RE: Paid app: declared devices accepted at upload, then not listed. Is there a canonical monetization-supported device list?

flocsy🤠 — Tue, 01 Sep 2026 13:17:28 GMT

Use the VSCode editor for the manifest, there it's very clear what is supported and what isn't.

RE: Paid app: declared devices accepted at upload, then not listed. Is there a canonical monetization-supported device list?

6358344 — Tue, 01 Sep 2026 13:13:44 GMT

Not an answer, but a data point from the free side that may narrow down where your devices are being dropped.

I hit a silent device loss last week on twelve free watch faces, and the cause was upstream of monetization: minApiLevel. My manifests declared 72 products, but with minApiLevel="3.4.0" the store export built only 84 targets. Lowering it to 3.0.0 built 107. Eleven declared devices were being dropped by the compiler and never reached the .iq at all.

The part worth knowing: monkeyc -e gives no warning for this. It only errors if every device fails ("No exportable devices are supported by the project"). Building for a single device does report it clearly:

ERROR: Device 'vivoactive4s' does not support API Level '3.4.0'

Two things that cost me time and might save you some:

1. The real API level per device is in %APPDATA%\Garmin\ConnectIQ\Devices\<id>\compiler.json under partNumbers[].connectIQVersion. Not deviceVersion, which is a git hash and looks nothing like a version.

2. Removing the attribute entirely is worse than lowering it. It builds for everything but stops validating APIs — it accepted a Graphics.getVectorFont call (API 4.0) targeting a device that maxes out at 3.0.12.

Worth checking whether your MARQ and Descent Mk2 units actually made it into the .iq before assuming it is the monetization filter. Compile for one of them individually: if it is an API-level drop you will get the explicit error above, and if it builds fine then the loss really is happening later, at the store layer, which is what you are describing.

Either way your underlying request stands, and I would add my voice to it: a canonical list of monetization-supported devices, and an upload warning when declared products are silently excluded. Right now both layers fail quietly, and the only way to find out is to compare the published listing against your own manifest.

Monetization: is there any path for a developer resident in Colombia? (and is the supported-country list current?)

6358344 — Tue, 01 Sep 2026 12:49:22 GMT

I have twelve free watch faces published on the Connect IQ Store and I would like to start selling two paid ones. I am a resident of Colombia, and I would rather confirm the requirement than submit an application that cannot be approved.

The Merchant Onboarding page states that the monetization system is available to developers with legal entities in the United States, Canada, Australia, Singapore and most of the European Union, and that if you do not live or are not incorporated in one of those countries you cannot sign up. Colombia is not on that list. The page also notes the list is subject to change, which is why I am asking rather than assuming.

Three questions:

1. Is there currently any route for a developer resident in Colombia to enrol? I note that Colombia does appear on the list of countries whose users are allowed to purchase monetized apps, so buyers here are supported even though sellers are not.

2. If I established a legal entity in one of the supported countries, would that satisfy the requirement while I personally remain resident in Colombia? The documentation asks individuals for proof of residential address and individual tax ID, so I cannot tell whether eligibility follows the entity's country of incorporation or my own country of residence.

3. Is the published list current? I have seen Mexico referred to as supported in at least one place, but Mexico does not appear on the Merchant Onboarding page. If that list is out of date, it would be useful for more of us than just me.

For context, this is a personal project, not a company. I would be enrolling as an individual / sole proprietor.

Thanks for any clarification.

Approved update is not showing in the public Connect IQ Store

4617860 — Sat, 29 Aug 2026 02:28:27 GMT

My Atlas Rhythm watch face update has been approved in the developer portal, but the public Connect IQ Store page still shows the old version (1.0.3).

The developer portal shows the latest version as approved, while the public Store page has not updated for more than a week.

Has anyone experienced an approved update not appearing in the public Store? Could Garmin please check the publication/synchronization status for this app?

App UUID: AD9DCDA5-CA91-4145-ABE3-CB1BCFCE946C

Possible review bombing on multiple Connect IQ apps

Aleksandr Ivanov — Wed, 19 Aug 2026 02:12:56 GMT

Today two of my watch faces suddenly received many 1-star reviews:

TabloA — 25 reviews
Tablo3 — 19 reviews

All Garmin notification emails contain the same meaningless text: “a”, from one user.

The reviews are not visible in the Connect IQ Store, so I cannot flag them individually.

This looks like coordinated or automated review bombing.

Has anyone else experienced this recently? Could someone from the Connect IQ team investigate?

TabloA:
https://apps.garmin.com/apps/caf05d04-f6ff-4925-8156-6e149a177634

Tablo3:
https://apps.garmin.com/apps/cf917f0b-f5f9-4377-834c-34f9954842a7

RE: Possible review bombing on multiple Connect IQ apps

SW88 — Wed, 26 Aug 2026 21:38:41 GMT

I had a clear spam review recently which made no sense and made fun of a dead political figure. Reported it, but no response from Garmin yet….

“absolutely horrible i wanted a Charlie kirk hood version and this is not it. very disappointing and i will contact the ceo of garmin watch display app. anybody reading ts your a lil squirt. peace ✌out btwissle”

RE: Getting Approval for ‘Medical App’

9747506 — Wed, 26 Aug 2026 12:01:25 GMT

okay thanks for the tips 🙂

Getting Approval for ‘Medical App’

9747506 — Mon, 17 Aug 2026 16:19:38 GMT

Hi All,

I built an app meant to be used by medical staff (such as myself). It’s relatively simple and basically functions as a note pad / watch / timer.

When I submitted the app, I found out about the difficulty getting ‘medical apps’ approved for the IQ store. I can absolutely understand that, as many may require FDA oversight.

However, my app very clearly falls into the ‘Not a medical device’ based on several factors that are listed on the FDA website. I tried changing my listing to match those factors, but it still is considered not approvable apparently without FDA approval?

Getting FDA approval for a non-medical device seems… overkill? Not to mention certain aspects could be costly.

I’m wondering if anyone has experience with this, or if there is anyone specific from Garmin who I could speak with about this, given the clear direction from the FDA that my app does not qualify as a ‘medical device’ and would not require regulatory oversight or approval.

Thank you!

Atlas Rhythm — a personal-baseline watch face for daily rhythm awareness

4617860 — Wed, 26 Aug 2026 08:35:12 GMT

Hi everyone,

I’ve released Atlas Rhythm, a Connect IQ watch face built around one simple idea: daily health signals are more useful when compared with your own usual pattern, not a generic score.

Atlas Rhythm shows four personal-deviation indicators:

Energy: recent Body Battery change rate versus your usual rate at the same time of day
Stress: today’s time-weighted Garmin stress level versus your personal same-time baseline
Recovery: overnight Body Battery recovery within your configured sleep window
RHR: Garmin’s 7-day average resting heart rate versus your personal baseline

The center indicator is not another weighted 0–100 score. It simply shows how many of the four available indicators remain within your normal range, together with a short action cue.

A few implementation notes:

Personal baselines use recent valid history, median values, and MAD-based deviation bands.
Stress coverage and missing sensor data are handled explicitly; missing values are not treated as low stress or normal data.
The watch face supports English and Simplified Chinese, with a language setting in Garmin Connect.
Sleep settings only define the recovery analysis window; they do not change the watch-face layout.
This is a personal-awareness tool, not a medical device or a substitute for medical advice.

I’d especially welcome feedback on the readability of the four-card layout, the English terminology, and how the watch face behaves across supported Garmin devices.

Thank you for taking a look.

RE: Getting Approval for ‘Medical App’

flocsy🤠 — Wed, 26 Aug 2026 07:40:33 GMT

I'm not affiliated with Garmin, just another hobby dev, but I don't think they do review the apps every time we upload a new version.

I don't see how your app works or looks, but it sounds like there's some thematical menu in there. It would complicate it a bit but you could make that as a user providable thing. They could go to a website where they could pick the topic and then the app would download a json configuration for that topic. This way your app is kept general (you might be surprised what future uses other users will have) but it still gives the same solution as it does now, the medical part however is decoupled to the website.

But if I were you I'd just try the 1st simple version, 2nd update with new features. If for some reason the update will be blocked you can still do the downloadable configurations later

RE: Getting Approval for ‘Medical App’

9747506 — Mon, 24 Aug 2026 21:35:58 GMT

I had considered this; that’s all it *really* is, but because the app has a bunch of medications and medical procedures listed, I don’t think I could do that without scrapping all of that stuff and leaving behind almost nothing. I’d rather not do that.

And then of course if I did scrap it just to add it back in, I imagine that would not necessarily go over well.

RE: Getting Approval for ‘Medical App’

flocsy🤠 — Mon, 24 Aug 2026 20:55:35 GMT

Try to rebrand it as a note taker, upload as a new app, let it be approved, then edit the description and add a few example use cases, and there mention your use case amongst others

RE: Fees should be included in the sales report

Manuel B. — Fri, 21 Aug 2026 13:43:48 GMT

Yes, that is what Garmin told me in response to my initial request.

the changes we made to the report were intended to replace the reports that Nick was creating for you. We’re certain we can solve this issue. Is your payout currency in EUR?

When I asked when the fix will be available...

We have created a ticket to have the store team update the report to provide all values in your default currency. It’s unclear when this will be prioritized, but that will ultimately provide what you need.

Then I asked for a manual report

We will forward this to have a report generated—it will likely not be available until sometime next week.

This was 5 weeks ago and now they are ghosting me.

Fees should be included in the sales report

Manuel B. — Wed, 16 Jul 2025 03:51:13 GMT

Currently only the developer share is included in the sales report. For proper tax filing the transaction fees are a necessity.

Tried contacting ConnectIQAppAdmin@garmin.com several times but keep getting ignored.

RE: Fees should be included in the sales report

TitanicTurtle — Fri, 21 Aug 2026 09:49:54 GMT

Yeah, I guess I'm in the same boat, my tax return isn't overdue yet, but eventually I'll run into the same problems.
The fact that these tax reports are no longer distributed via "Box" is new to me, but it explains why Q2 wasn't delivered.
When I manually request a report through my dashboard, it says it should be delivered in a few days, but it hasn't worked that way once this year.
I think I'll follow Roboleo's suggestion and draw up an invoice for each month.
If they ask for more documents after that, well... that'll be interesting.
I have to admit, though, that I haven't contacted Garmin about this yet, I should probably do that.
But judging by the posts here, the chances of success probably aren't very good.

RE: I updated my widget MySteps. Is it possible to know the exact number of users/downloads?

1057439 — Sat, 15 Aug 2026 13:31:40 GMT

The 700 is based on an estimation using the statistics about the versions and devices. So this is not unique users but an estimations of the number of downloads

I updated my widget MySteps. Is it possible to know the exact number of users/downloads?

1057439 — Wed, 12 Aug 2026 17:04:17 GMT

I created a widget that can help you with the 300,000 steps challenge every month? .

How MySteps helps you complete the 300k steps challenge:

Shows your current month’s progress towards the fixed 300,000-step goal, using a circular progress ring for 0-100% and a second ring for any extra steps beyond today’s target
Summarises the month with:
Month Challenge
- Total steps taken
- Days left in the challenge
- Required steps per day for the rest of the month
- A clockwise ring around the edge showing your progress
- Uses today’s live step count to show your daily progress by filling the feet
- If you take more steps, a counter-clockwise ring appears (100% of today’s target closes the ring)
Offers optional onboarding if you install later in the month (after day 7), so missed steps can be entered accurately
Enter only the number of steps completed before today; do not include steps taken today
Celebrates when the 300k target is reached with a one-time monthly animation. Tap it to return to the default screen
Includes a history screen where you can see totals for previous months. Tap to open it, or tap again to return to the default page

From the statistics I think I can calculate that I have now around 700 downloads. But I would like to know the exact number. Why does Garmin not show that on the statistics page?

emulator sets sensor history samples time into future

Yeti II — Fri, 14 Aug 2026 13:32:17 GMT

I've switched today from SDK 7.4.3 to 9.2.0 today and was surprised why the stress history and body battery history don't work correctly. Finaly I understood that the `when` moment of every datapoint is set in the future

This only happens in the simulator, real watch seems to be OK. With the SDK 7.4.3 works fine

here the times that I get when reading the last hour of the body battery
sample:1786713990 now:1786713989
sample:1786714050 now:1786713989
sample:1786714110 now:1786713989
sample:1786714170 now:1786713989
sample:1786714230 now:1786713989
sample:1786714290 now:1786713989
sample:1786714350 now:1786713989
sample:1786714410 now:1786713989
sample:1786714470 now:1786713989
sample:1786714530 now:1786713989
sample:1786714590 now:1786713989
sample:1786714650 now:1786713989
sample:1786714710 now:1786713989
sample:1786714770 now:1786713989
sample:1786714830 now:1786713989
sample:1786714890 now:1786713989
sample:1786714950 now:1786713989
sample:1786715010 now:1786713989
sample:1786715070 now:1786713989
sample:1786715130 now:1786713989