New Merchant, first update with pricing and buy buttons greyed out

I recently got approved for the Garmin Merchant Monetization system and have now updated all of my watch faces on IQ to payed for watch faces.  They have all been approved and I was told that it could take 0ne more day to update them on the IQ site.  Some are now appearing and I found 1 which is a brand new one, with what appears to be a fully functioning buy button at https://apps.garmin.com/apps/7e644318-669d-4aa6-bb39-302fa629ade3

The others however have greyed out Buy buttons that dont do anything lik e this one apps.garmin.com/.../61cfadd8-6d16-4574-b33d-fb2a900a512e

Can anyone explain whats going on here? How can I fix this?

  • You cannot do this. Garmin determine what are the compatible devices and list them. If one of those devices in the list is monetized and “not supported for monetization” these devices are hidden and the ones that can be monetized have their buy buttons greyed out!

  • That's why you use two apps.  One with devices that support Garmin Payment and one for the others.  This was discussed back when payment was introduced

    In this case you have one app for the i3 devices that support garmin payment, and a second app for the i2 devices that don't support garmin payment, where each has their own download count and rating.

  • Honestly with all the mess around this + the known problems with Garmin why would anyone use Garmin Pay and not a well established 3rd party payment platform?

  • How could a developer "remove" this app?

    Developers are able to delete their apps at any time. It would absolutely be a bad experience for end-users for the reasons you exist. We do retain "abandoned" apps, which occurs when a developer deletes their developer account without removing their apps. I'll have to ask whether we have any intent to retain paid apps even if a developer wants to delete them.

  • Why only paid apps? I think every app should be retained for settings, fitcontributions.xml forever. They should not come up in the search, and even if someone has a link to the app it should display 404. But as a user if I started using an app, I don't want it to become useless because the author deleted it.

  • The solution is very very simple.

    Garmin should preferably stop removing users watch Faces if it is removed from the IQ Store.

    Or

    Garmin should preferably stop removing users watch Faces if it is removed from the IQ Store and the developer is no longer part of the monetization program.

  • It's not as simple as that, because if a dev removes the app from the store he expects to be no more new downloads. I would even say that if a user has an older version installed before the dev removes it from the store, then it's even ok that the user will not be able to upgrade to the "latest" version but can keep using the version they had "forever'

  • Developers are have always been able to remove their own apps from the store at-will. If a user installs an app that is later deleted, it remains on the device a long as they don't uninstall or reset the device. If for some reason the user is not already on the most recent version, they won't be able to update. Any store dependencies like app settings and custom FIT contributions will no longer function, but the app will continue to otherwise work.

    This has not changed with monetization, and I don't know of any plans to change this scheme. I don't believe this happens very often, but I don't have any metrics to prove one way or the other. Based on my observation, it's more likely for a developer to just abandon an app than to delete it.

    In the case of a developer monetizing with our solution who abandons their app, it seems likely they will simply not renew their merchant account, which would result in their apps remaining on the store for free once their merchant account expires.