How to compile a 735xt app with 2.2.1

Hello,
I'm using the latest version of the simulator and 2.2.5 SDKs on my mac.
I need to test an app for a 735xt with version 2.2.1 but only appears the option to use 2.1.x ...

Where can I modify the settings to force the simulator to use 2.2.1 for this device? Modifying devices.xml didn't work for me ...

Thank you!
  • hi,
    there isnt a version 2.2.5.
    there was a 2.1.5, and then, the first 2.2.0beta was released. and currently the latest version is 2.2.1. (Nov 8, 2016)
    are you sure you have the latest one installed?

    EDIT:
    actually i have just rememeber, that when i updated my 230 to 7.1, it was supposed to support CIQ 1.4.1. but in the simulator i still see 1.3.x. i opened a post for this. i guess this is the same question.

    EDIT2:
    this is the post:
    https://forums.garmin.com/showthread.php?365871-how-to-build-using-Connect-IQ-1-4-1-SDK
    and Jim told me that id be doing right be using the latest available SDK. this should be valid for 2.2.1 too.
  • Ok, a couple of things here. On the watch itself is the CIQ VM (virtual machine), and what you develop with is the SDK. There are many times that a VM and SDK version don't match, and different devices have have slightly different VMs. In the extreme case, a watch could have a 1.2.1 VM, but the current SDK for it is 2.2.1.

    When it comes to the 1.4.1 VM on the 230 and the 2.2.1 SDK, I've seen only one call that is new in 1.4.1 - toNumberWithBase(). Before it was only for devices with a 2.1.x VM. The 2.2.1 SDK also has a few things only for devices with a 2.2.x VM, such as PersistedContent

    As far as minVersion, you don't really need change that often. If the min is 2.1.x, it will work on 2.2.x, but if you could set it to 2.2.1, it couldn't be installed (from the store) on watches with 2.1.x, even if it would work just fine. It's really a "minimum version" and not a "VM version to test with".

    A case where is was used is with FitContributor, which was new in 1.3.x/2.1.x, and in relation to the APAC version of some devices. If you look at "supported devices" in the app store, you'll often see something like "forerunner 235" and "forerunner 235J". The "J" version is the APAC version, and APAC versions are a bit behind FW versions from the non-APAC. When you set a target for a project, you'll also notice that there is only a 235, and not a 235J. And there was a time where the 235 haa 1.3.x VM while the 235J had a 1.2.x VM.

    So if you were using FitContributor, you could set the minVersion to 1.3, and then the store wouldn't even show it as available for the 235J devices (it's all part of the App Exporting, as it actually includes the non APAC and APAC build there, and with a 1.3 min, it didn't include devices that weren't at least 1.3).

    So basically, if it works on 1.3.x, it will work on 1.4.x, and if it works on 2.1.x it will work on 2.2.x, and you don't need to test a specific on (1.3 as well as 1.4, or 2.1 as well as 2.2) in the sim. And you don't want to change things in devices.xml, as that could mess with what's in the .iq and whats not, and maybe confuse the app store.
  • hi,
    there isnt a version 2.2.5.
    there was a 2.1.5, and then, the first 2.2.0beta was released. and currently the latest version is 2.2.1. (Nov 8, 2016)
    are you sure you have the latest one installed?


    I did a typing mistake :p
    I've the 2.2.1 sdk installed.

    I'll try your solution!

    Thank you!!!