bug: venusqm CIQ version isn't updated

noticed https://developer.garmin.com/connect-iq/compatible-devices/ has 0 as the 3rd version number for all devices, regardless of what's in compiler.json or on the real device with latest firmware. I feel like it might be intentional

It is. I'll create a ticket to just list the major and minor and see where it goes.

On a physical venusqm the API level is 3.3.6, but in compiler.json it's only 3.3.1

Firmware and CIQ versions are only updated in the JSON when there's something new in the API. The intent of the firmware version is to ensure that apps that use new APIs do not crash on devices that haven't been updated.

With yesterday's 8.1.0 release, a bunch of device configurations were updated to CIQ 5.1.0 and their firmware set to what supports CIQ 5.1.0. Since devs will (hopefully) want to use the new 8.1.0 APIs, the configurations were updated to ensure that end users cannot install apps that are using the new APIs when they do not support them. Yes, there are other ways this could be handled but this is how the system works.

On the other hand, the JSON configurations were not updated with the November device releases. There was nothing new in the API to warrant having developers download new configurations, then wanting to rebuild their apps and release an update, then force end users to update their watches to download the apps which are essentially the same as before. For the end user this wouldn't have accomplished anything.

With all that being said, there was nothing exciting between 3.3.1 and 3.3.5. But 3.3.6 introduced the GNSS configuration API. I'll create a ticket to look into why this wasn't updated. It may have been overlooked, or there may have been a reason it wasn't updated.

noticed https://developer.garmin.com/connect-iq/compatible-devices/ has 0 as the 3rd version number for all devices, regardless of what's in compiler.json or on the real device with latest firmware. I feel like it might be intentional

It is. I'll create a ticket to just list the major and minor and see where it goes.

On a physical venusqm the API level is 3.3.6, but in compiler.json it's only 3.3.1

Firmware and CIQ versions are only updated in the JSON when there's something new in the API. The intent of the firmware version is to ensure that apps that use new APIs do not crash on devices that haven't been updated.

With yesterday's 8.1.0 release, a bunch of device configurations were updated to CIQ 5.1.0 and their firmware set to what supports CIQ 5.1.0. Since devs will (hopefully) want to use the new 8.1.0 APIs, the configurations were updated to ensure that end users cannot install apps that are using the new APIs when they do not support them. Yes, there are other ways this could be handled but this is how the system works.

On the other hand, the JSON configurations were not updated with the November device releases. There was nothing new in the API to warrant having developers download new configurations, then wanting to rebuild their apps and release an update, then force end users to update their watches to download the apps which are essentially the same as before. For the end user this wouldn't have accomplished anything.

With all that being said, there was nothing exciting between 3.3.1 and 3.3.5. But 3.3.6 introduced the GNSS configuration API. I'll create a ticket to look into why this wasn't updated. It may have been overlooked, or there may have been a reason it wasn't updated.

Thanks for the explanation!

As you may know, the topic of device CIQ / firmware versions in compiler.json comes up a lot in the forums, and there's a lot of discussion / speculation about exactly why things are the way they are, so it's good to hear some clarifying details from the CIQ team.

_psx_ Kyle.ConnectIQ's comment might interest you