Connect IQ SDK and Plugin v2.2.3

The Connect IQ 2.2.3 release is now available for download!

You can get it one of two ways:

  • Use the Connect IQ SDK Manager in Eclipse, by clicking the Connect IQ menu, selecting Open SDK Manager, and then clicking the Download button for Connect IQ SDK 2.2.3 released December 22, 2016.
  • Download directly from our developer site at http://developer.garmin.com/connect-iq/sdk/

General Changes

  • Add fenix 5, fenix 5S and fenix 5X device support to SDK and samples.
  • Remove support for the “Round 240x240 Family” preview device. Existing apps should be directly migratable to either the fenix 5 or 5X and will be assisted by the Eclipse plug-in or console output.
  • Fix issue where animations that are started in AppBase or View initialize functions did not work in some cases.
  • Fix loading lag for apps that do not have settings.
  • Fix issue where deleting a non-existant mailbox would cause the app the crash.
  • Prevent device crash that could occur in rare conditions during startup.
  • Prevent device crash with FitContributor.setData() that could occur under certain circumstances.
  • Send a burst error when an Ant.GenericChannel burst fails instead of crashing the app.
  • Fix an unexpected type error that occured when attempting to access nested class members from the parent.
  • Properly handle key presses on System.exit() to prevent unexpected device behavior.
  • Update device minimum firmware versions.
  • Many documentation improvements and bug fixes.


Simulator Changes

  • Close a widget when a NEXT_PAGE or PREVIOUS_PAGE behavior is issued on the base view to match devices.
  • Fix issue where power meter support was not available on some simulated devices.
  • Support Enhanced Speed / Altitude (D2 Bravo / Titanium) in simulator FIT parsing.
  • Prevent failure to auto-pop a view when the back key is pressed if there was no delegate.
  • Fix issue where Attention.vibrate did not work on the MacOS Simulator.


Known Issues

  • Known issues will now be tracked in the Connect IQ forums
  • A note for others about the f5s, f5, and f5x:

    In testing things I see fonts are different for the 5s,5, and 5x than they are on the other round watches, so you want to check them out in the sim, and not just check them as targets, build a .iq, and upload to the store. :)

    The developer blog says that auto-migration won't be used for the f5 devices, and the font difference is likely involved.
  • so you want to check them out in the sim, and not just check them as targets, build a .iq, and upload to the store.


    That's always good advice, whether adding support for a new device or making changes -- always test against all your supported devices. :)

    To add on to Jim's comment about the fonts, I did some testing and found that although the Fenix 5/5X screen is 240x240 pixels, there is actually less screen real estate for text (as compared to the fenix 3) when using the built-in fonts because of the font/sizes chosen. This is most noticeable with tiny vs xtiny: they are both the same size, but xtiny is regular weight whereas tiny is bold weight. That said, the fonts will be slightly more crisp thanks to the extra size (22 pixels) of the fenix 5/5X.

    This seems a bit of departure from the past where the fonts were more consistent between devices, but can be solved by extracting the font size used into device specific files used in tandem with a build file for each device.

    Cheers,
    Douglas
  • .. so you want to check them out in the sim, and not just check them as targets, build a .iq, and upload to the store. :)


    Have just tested & updated Segment to support the 240x240 screen. Have added the fenix5, 5s, 5x as products in the manifest - however - don't see them as supported devices in the store.

    Assuming the store still needs an update :)
  • It may be that displaying them isn't "turned on" yet, as the new watches won't be shipping for a while. (people don't have the devices yet) I updated something with 5s,5,and f5x support and noticed it too.

    Since the app store didn't reject the upload, all should be fine.
  • Hey Everyone,

    I'm glad everyone is having fun playing with the new devices in the Sim. The product team knows about the TINY vs XTINY font thing. That's on hardware as well. You should be able to upload for the new fenix 5 devices, but they will not show anywhere in the store yet as Jim is correct that they have not been turned on.

    Thanks,
    -Coleman
  • Hi,

    I seem to be having the bug in the below link with 2.2.3. (I am in the settings editor and I can adjust a "list" setting fine, but when I go to click "Send Settings" button it reverts the list option back to the default.

    I guess this bug will be added to future SDK releases? (the last post in the below forum link says that the fix would be included with future SDK releases, but this was posted on the same day as the release of the 2.2.3)

    https://forums.garmin.com/showthread.php?367020-App-Settings-Editor-Issue

    Thank you; didn't know where was a good spot to ask this question as the bug thread has been locked, and wasn't particular about which version of the SDK it would be included with.
  • Hi,

    I seem to be having the bug in the below link with 2.2.3. (I am in the settings editor and I can adjust a "list" setting fine, but when I go to click "Send Settings" button it reverts the list option back to the default.

    I guess this bug will be added to future SDK releases? (the last post in the below forum link says that the fix would be included with future SDK releases, but this was posted on the same day as the release of the 2.2.3)

    https://forums.garmin.com/showthread.php?367020-App-Settings-Editor-Issue

    Thank you; didn't know where was a good spot to ask this question as the bug thread has been locked, and wasn't particular about which version of the SDK it would be included with.


    Thanks for reaching out.

    This issue has been addressed and should not still be happening. Eclipse can be particularly "sticky" when it comes to what has been installed. I personally had this issue persist after the patch was applied. I actually had to dig through my directories and get rid of some of my Eclipse config files that were still forcing aspects of old installs of my CIQ plugin. In short I would make sure to clean out your workspaces, make a backup of project, try getting rid of Eclipse and any trace config files, then reinstall Eclipse, and re-import your projects. It is a bit of a process, but it should get you going again. Unfortunately we don't have any power over what Eclipse holds on to in regards to our old installs. Hopefully this resolves the issue for you!

    Thanks,
    -Coleman
  • Suddenly found v2.2.4 is available (release date stated as 1 Feb).

    General Changes
    Fixed a compiler bug where launcher-icon resources could not be properly overridden using device families.
    Added support for APAC Fenix5 devices
    Updated minimum firmware versions for the vivoactive HR
    Simulator Changes
    None

    *simulator file has few kilobytes difference however. Some minor changes in monkeybrains.jar, one major correction in documentation (Activity - Info - functions became available in 2.1.0, not in 1.2.10), one quick note added for SimpleDataField and DataField:
    The system will call the
    onUpdate() method inherited from View when the field is displayed by the
    system. Note that compute() and onUpdate() are asynchronous. There is no
    guarantee that compute() will be called before onUpdate(). Because there is
    no guarantee of calling order, variables should never be initialized in
    compute().