• State Not Answered
  • Replies 4 replies
  • Subscribers 6 subscribers
  • Views 285 views
  • Users 0 members are here
Options
Related

Same watch model, two users: one sees my published app in the mobile store, the other doesn’t

3473712

Hi,

My app Pumpee (Device App, app ID 7721b878b85a4f2db0d55042fe1b12bb) is published and approved, but two users with the same watch model get different results in the Connect IQ mobile store.

User A — Venu 3S paired, Connect IQ app on Android: Pumpee does not appear at all. Not in search by exact name, not in the device’s app list.
User B — same model, Venu 3S: finds and installs it normally.

Store page: apps.garmin.com/.../1495ee1c-8e47-432e-9a96-89c6e9946ca5

What I have already verified myself, so we can skip the usual first round:

The listing is APPROVED, latest published version 1.9.
Venu 3S is explicitly present in the “Compatible devices” list on the published page.
The manifest declares minApiLevel 3.0.0 (a Venu 3S ships well above that), permissions Fit, Positioning, Sensor, Communications, and 116 products including venu3s.
On the web store in a desktop browser, the app is fully discoverable: searching “pumpee” returns it 3rd, and “pump foil” returns it 7th out of 991 results.
The app has real downloads and a review, so it is reachable for some users.

So the listing itself looks correct, and the problem appears to be per account or per device registration, not per model.

My question: once a device model is listed as compatible, what else is evaluated when the Connect IQ mobile app decides whether to show an app for a given user’s watch? Is the watch’s firmware CIQ runtime version taken into account, the account’s country, or a per-account index that can go stale? And is there anything a developer can check or trigger on their side?

I can provide both users’ watch firmware versions, Connect IQ app versions, phone OS and account regions — tell me which of those would help most.

Thank you.

  • 0

    Country is. Is your app country restricted? Is it Garmin Pay app? Because then even if your app is not restricted by country the payment is

  • 0

    t used to be that even for free apps, if the app didn't display the dev's email and location the proper way, they weren't available in the UK.  t was a UK restriction.

    Here for example is a Garmin app:


  • 0 in reply to jim_m_58

    Update, with more data:

    On the phones where Pumpee doesn't appear in search, opening the listing's direct link in the Connect IQ app shows "server connection error". On a phone where it works, the same link opens the listing normally. Both users live in France and have the same watch model (Venu 3S); mine runs software 17.05, above the 16.07 my package requires. On a failing phone, Pumpfoilytics shows up fine. My listing has no country limits and the app is free.

    The only field I can see that differs from comparable apps: developerDisplayName is null. Pumpee is my first app (published September 2026).

    Could a first-time developer's free app be hidden this way for EEA accounts, with the direct link returning a server error? Or could the empty developer name break the listing in the mobile app?

  • 0 in reply to 3473712

    Solved, thanks to both of you: the hint about developer details was the right one.

    My developer profile had no display name (developerDisplayName was null in the store data). The web store didn't mind, but on some phones the Connect IQ app refused the listing: Pumpee was missing from search, and the direct link returned "server connection error". As soon as I set a developer name in the dashboard, the app appeared on a phone that couldn't see it before. No new build needed.

    If your app is approved but some users can't find it in the mobile store, check that your listing shows a developer name under the title.