Missing CIQ 3.2 device in garmin store (Fenix 6 Pro Solar)

How long has it been since you updated your devices with the SDK Manager?

It could be missing that the device now has CIQ 3,2

Can you select 3.2 for it when you run it in the sim using a run configureation?

Not sure about the time (a few days ago) but I'm quite sure that both versions are build with the same version...

Would you suggest to upload a new version and check if this fixes the problem?

And I can't select this device directly - I can only select the 5 groups from my screenshot above...

There's something with setting the minimum to 3.2.0 in your manifest.  This could be your devices are old, or could be that device is still on 3.1 as far as the SDK is concerned.

One way to check, is for that target see if you can select 3.2 in the run config in eclipse.

I selected the target device that contains the Fenix 6 Pro Solar and am able to select target 3.1.X and 3.2.X and I can start the sim with the 3.2.X target successfully...

I just tried to rebuild the watchface and upload it again - without success, the store still shows the same supported devices.

Have you check your devices are current?  It only takes a few seconds.

How can I? If I open the SDK Manager I just see that all devices are installed - no version info nor anything that indicates a possible update. I've enabled auto updates for the SDK and the devices.

I started the SDK manager before the last build though to check if I can update anything manually there, but could not see anything.

I have the same behavior with my apps but I'm wondering if it's more of a labeling problem than anything else.

In the manifest of two of my apps, I support the whole F6 range. One app requires CIQ 3.1 and the other 3.2. As with Michael, on the store, the list of F6 device for my 3.1 app is much bigger that my 3.2 app. 

Additionally, in the manifest, you cannot dissociate support for F6 Pro and F6 Pro Solar: it's the same tick-box

I'm assuming (probably wrongly) that a F6 Pro Solar owner will "see" and be able to download any F6 Pro app, but since Garmin have removed the "by device" browsing capability of the store, I don't know how to verify this.

I run the sdkmanager each time I start Eclipse to make sure I'm up to date with device configuration. On a side note , the F5X+ has CIQ 3.2 since more than a month, but the sdkmanager does not reflect that at the moment. If I want to publish my 3.2 app for the F5X+, I would need to change the manifest to 3.1 and then add the F5X+. There are other devices that have received 3.2 but are not up to date in the sdkmanager and it's a tedious job to go to each device's forum to try to guess which version of CIQ is supported on which device.

Something that also can come in to play is auto migration. If a new device is created and you have the migrate flag on then it will add the new device but if you recompile with an old SDK that migration is undone (it would need to migrate again)

ars.fabula said:

I'm assuming (probably wrongly) that a F6 Pro Solar owner will "see" and be able to download any F6 Pro app

As far as one of my users told me not, that's the reason for this question. I've even send the link to this user and he tried to open it in the browser and still it tells him that his device is not supported.

Setting a min CIQ version can be tricky.  For example, a ROW device may have 3.2, but an APAC version of the same device can have 3.1.  Or the SDK thinks a device has 3.1 where the firmware for that device has 3.2.

That said, all my apps have a min of 1.2, and I restrict the devices I support, and in addition, I make use of "has" for features.

What did does is prevent crashes on devices that may not have a feature and can display a message ("weather not available" for example), and can easily handle the case where the SDK thinks a device is on 3,1 but there's new FW that brings it to 3.2.  

It's next to impossible to follow FW on APAC devices, and by doing this, as a dev you don't really care.  The feature will start working when the device gets the new FW, without taking any action or there's an update for devices in the SDK.