Connect IQ 2.2.0 Public Beta!

The Connect IQ 2.2.0 public beta 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.0 released October 6, 2016.
Download directly from our developer site at http://developer.garmin.com/connect-iq/sdk/

There is also a new Eclipse plug-in version to support some of the new features in the 2.2.0 SDK, so be sure to install it, too, if you use Eclipse as your development environment. You can easily check for plug-in updates in Eclipse by clicking Help > Check for Updates.

This beta will allow you to develop, simulate, and build apps to side-load to your devices that use the new 2.2.0 features, but the ability to export apps for submission to the app store is disabled. Once this release is out of beta, we'll re-enable the app export features.

General Changes

Change assertEquals(), assertEqualsMessage(), assertNotEquals(), and assertNotEqualsMessage() to use .equals() instead of the == operator.
Add access to saved waypoints, courses, and workouts on a device with the PersistedContent module. See the Programmer’s Guide for more details.
Deprecate the PersistedLocations module. Use PersistedContent.saveWaypoint() instead.
Add support for Bike Light status and control using ANT+.
Add support for Bike Power using ANT+.
Add support for bursting in Ant.GenericChannel.
Add support for downloading FIT files and loading them onto the device. See the makeWebRequest() section in the Programmer’s Guide for more details.
Allow a watch-app or widget to open another CIQ app or native application using System.exitTo(). See the Programmer’s Guide for more details.
Optimize apps by having the compiler fold constants into a single value. var number = 4 + 5; will now compile to var number = 9; instead of performing an add operation.
Clean up samples to only support devices that can run them.
Several API / documentation fixes
Add Call to Parent’s initialize() in RunNoEvil
Limit the size of an app’s mailbox from a partner app to 8kb.

Simulator Changes

Simulate navigation data.
Simulate Accel and Mag data.
Save waypoints created with PersistedContent.saveWaypoint().
Simulate APIs available to the device being run. For example, Pressure History is no longer available to the Forerunner 735 in the simulator.
Support pairing Bike Lights.
Fix UTF8 strings in memory window

Known Issues

If an Exception is thrown from a catch block, the finally block of the current try/catch/finally will not be executed.

Brandon.ConnectIQ over 8 years ago

It's unlikely that we'll release a second, updated beta at this point, and unfortunately I don't have a date for the final release just yet. It should be soon. :)

a1234.garmin over 8 years ago

SDK manager forgets about downloaded item.

At the same time compiler can do job and project properties can be set to 2.2.0 SDK when path is overwritten manually in settings.

All updates performed. Mars2 used.

peterdedecker over 8 years ago

Add access to saved waypoints, courses, and workouts on a device with the PersistedContent module. See the Programmer’s Guide for more details.

This functionality seems very much geared towards being able to call System.exitTo. It's a step in the right direction but...

It would also be usefull to also have acces to (summary) info of workouts (eg type, distance, duration, etc...), just getting the name and id there is far from usefull. Same goes for courses and waypoints, where more info would also be usefull.

At the moment App developers are unable to create a widget such as "My Day" that's natively on Garmin Connect, having access to an API as described in the previous paragraph would at least allow that.

Brandon.ConnectIQ over 8 years ago

SDK manager forgets about downloaded item.

At the same time compiler can do job and project properties can be set to 2.2.0 SDK when path is overwritten manually in settings.

All updates performed. Mars2 used.

Thanks--I think we've already addressed this issue, but I'll double-check it to be sure.

Former Member over 8 years ago

I appreciate the clarification--we'll get in investigated. :)

Any updates on the nameOfNextPoint access on Edge devices?

mappicus over 8 years ago

Forerunner 735XT and Chronos toIntent()

The Forerunner 735XT and Fenix Chronos support Biker and have a basic route map capability: will Route.toIntent() and Course.toIntent() work on them?

Thanks.

a1234.garmin over 8 years ago

I have proposition for App Export wizard improvement. Current version does not store "project - export path" connection. This means if I need to export some projects to different folders, I need every time to select output directory.
Probably this can be done when wizard will store such information for every project.
Also I noticed that wizard currently stored only one place and this place is not changeable, it appears every time I launch wizard. At least recently used location will be better than current implementation.

Former Member over 8 years ago

Hi James: Yes, this feature should be fully functional by the time the 2.2.x SDK comes out of beta. In fact, we already have a fix merged and I've verified that it works.

Brandon,

A recent blog post mentioned that "EDGE devices support FIT content, and the Oregon/Rino products support GPX content".

Is this correct? So even with the final release of 2.2.x it won't be possible to download GPX content to an EDGE device?

This seems to contradict your statement that a fix for my issue was already merged?

Thanks,

James

Brandon.ConnectIQ over 8 years ago

Hi James--I have to eat crow a little on this one. I had overlooked the part of your question that specifically mentioned Edge. At the time, none of the GPX features were fully completed, and I was answering generally that we'd have them available soon.

However, just like you noted, Edge will only support FIT content and Oregon/Rino (likely all outdoor devices) will only support GPX. Originally, we had intended to make FIT and GPX available on all devices, but GPX support on Edge isn't really up to par and would lead to an inconsistent experience for end-users. That's the main reason for the split, and we want to address this in the future.

I apologize for my (unintentionally) misleading remarks!

Brandon.ConnectIQ over 8 years ago

Any updates on the nameOfNextPoint access on Edge devices?

There was a fix for the nameOfNextPoint issue put into Edge firmware in April (v11.xx), so if you're up to date on your firmware, you should already have the fix.