Acknowledged
CIQQA-4582

Edge devices not showing as compatible on public Store listing

App: Multiple Activity Popup Reminder (App ID: 7ca26c13-0097-4db1-9013-446883a1a04c)

Summary:
My app's Developer Dashboard shows Status: Verified, Signature: Verified, and a full list of compatible devices including edge1030, edge1040, edge1050, edge530, edge540, edge550, edge830, edge840, edge850, edgemtb, and edgeexplore2. However, on the public Connect IQ Store listing, no Edge devices show as compatible at all — not just Edge 1050, but the entire Edge line.

Troubleshooting done so far:
- Confirmed all relevant Edge product IDs are present in manifest.xml and show in the dashboard's compatible devices list
- Confirmed the app is Verified/Signature Verified
- Sideloaded the .prg directly onto an Edge 1050 via USB — installs and runs correctly, ruling out an actual code/manifest incompatibility
- Noticed the app's Store category was set to "Running" rather than "Cycling" — changed this to Cycling, thinking it might be filtering Edge devices out of Store browsing/search
- Submitted a new version (pure version bump, no functional changes) to force Garmin's pipeline to reprocess the listing, in case the category change alone didn't propagate

Current status:
Waiting on this new version to clear review. Once live, will check again whether Edge devices appear as compatible on the public Store page.

Question:
Is there a known interaction between the Store category field and per-device compatibility filtering that could cause an entire device family (Edge) to be hidden from the public listing even when they're correctly verified in the device list? Or is there another setting I might be missing? Happy to share screenshots of the dashboard's verified device list alongside the public listing showing no Edge compatibility, if that helps diagnose.

GrahamAEdwards

  • Okies an update. I have compiled the app again but edited manifest only for  uuid and edge devices, uploaded to store and when clicking on download I now see My edge 1050 to install to as an option, its also free, I personally think  is correct regarding the pay comment.

  • in reply to flocsy🤠

    Thanks for your valuable input I'm going to offer it for free for edge devices. see what happens 

  • This is a paid app (Garmin Pay), which IMHO isn't supported on the edge devices.

    However this is not the first developer reporting "bug" about this, not even the first this week actually. I think it would make sense if Garmin could somehow indicate this to the developer in the dashboard. 

    I'm not really sure what would be the best thing to do but here are 2 possible options:

    1. don't let us upload an iq file that contains unsupported devices if the app is paid. This would be the clearest option, and there are already (maybe not too clear) error messages for similar situations, like when we accidentally built for a preview device. The only theoretical downside of this could be (and I don't know if this can happen, but I'm sure Garmin will know) if it's possible to upload to devices that don't support Garmin Pay currently but in the future they'll be added and then the app becomes available on those devices as well. I can see why this could've been the case when Garmin Pay was announced., but it's hard to believe there will be existing devices added to Garmin Pay in the future...

    2. let us upload as the current behavior, but indicate it in the top of the dashboard that some devices are not supported because they don't support Garmin Pay (and the list of devices of course)

  • Thanks for acknowledging this (CIQQA-4582). For reference, here's where things stand on my end:

    - App: Multiple Activity Popup Reminder (7ca26c13-0097-4db1-9013-446883a1a04c)
    - Version 1.0.4 is live, category confirmed as Cycling, and Edge devices (including Edge 1050) are confirmed verified/compatible in my dashboard
    - Public Store listing still shows no Edge device compatibility
    - Sideloading directly onto an Edge 1050 works correctly, confirming this is a Store display/indexing issue rather than an app problem

    Happy to provide any further logs, screenshots, or a test build if that helps with the fix. Is there any visibility into rough timeline or priority for this ticket?