vivoactive APAC user cannot download CIQ 1.4 apps from the store

Hello everyone.

I have been receiving for some time reports from vivoactive users about this error message in the app store
"The app is not compatible with the selected device."

It took some time to get to the cause but I found the cause of the problem this week.
It was a lucky guess, and I was able to find the origin of the problem because the user informed its device is a Japanese model.

Garmin released the firmware update 4.40 for APAC vivoactive June 28, 2017 (almost a year ago) this update added support for Connect IQ 1.4.2

I looked into Devices.xml of SDK 2.4.5 released April 19, 2018, and for my surprise

<part_number connectIQVersion="1.4.1" firmwareVersion="440" number="006-B1907-00">
<part_number connectIQVersion="1.3.1" firmwareVersion="400" number="006-B2160-00">

The setting for the APAC vivoactive is still pointing to CIQ version 1.3.1.


That means APAC vivoactive users cannot download from the store apps that have 1.4 as the minimum CIQ version, since this version was not generated during the app packaging.

I have a question for the Gamin Team

While we wait for the fix in the SDK. Can I modify my DEVICES.XML file and copy the settings from the standard vivoactive (006-B1907-00) to the line of the APAC vivoactive (006-B2160-00) without risking any incompatibility or some issue in the store? I would like to make my apps available again to vivo APAC users as soon as possible.

Thanks in advance for your help.

Cheers,

Robinson
  • Do you have the minSdkVersion set for 1.4 in manifest.xml and do you need that? if you can remove the 1.4 restriction, that might be the simplest way to go.

    I checked a few of my apps, and in all of them, I left the min at the default, so minSdkVerion="1.2.0"
  • No Jim, I believe you did not read my message carefully.

    I am informing that the 1,4 ciq apps are not being generated to apac vivoactive users, preventing then from using the apps.

  • But is minSdkVersion set in the manifest to something other than 1.2.0? If so, that would explain why the .prg isn't being generated for that part number. If you can use 1.2.0, that could get the user going without having to wait for a fix in the SDK.
  • Thanks for the suggestion. But in my case it is not possible to run my app with ciq 1.2 or 1.3. If it was possible I would have done it by now.

    Garmin team, could you please verify if I can patch the devices.xml myself? I just want to be on the safe side.

    Thanks a lot

    Robinson
  • The only device I know of with 1.2 is the epix, so don't have that as a target and that's covered. I'm not sure what's still on 1.3 either, as I think everything is now at least 1.4, but the garmin folks will know for sure. (if the APAC va is 1.4, that kind of tells me everything else is) By using a "has" or checking monkeyVersion in the code, can your app handle 1.3?

    Have you checked with the user to see what's in "about" for both FW and CIQ version?
  • I appreciate your urge to help but we are missing the point here Jim.

    It is not an option to do any kind of maintenance in stable apps, that are being used by thousands of subscribers just to workaround a bug in the SDK. This kind of risk is not worth taking.

    Anyway, thanks for your suggestions.

  • Former Member
    Former Member over 7 years ago
    I will file a ticket to get the vivoactive APAC connectIQVersion corrected.

    I don't believe changing this value in the XML will allow the packaging tool to target the device. The packaging tool uses a separate embedded version mapping.
  • Hi Brian,

    I imagined messing with the SDK files would do no good.

    Thanks a lot for the information.

    Cheers!
  • Former Member
    Former Member over 7 years ago
    This was fixed in the 2.3.1 SDK version.