Connect IQ 2.1 SDK Preview!

Well that a SDK has a lifecycle is completely understandable. But in this case we are talking about the current flagship released only 5 months ago that has a SDK that is only supported for some months now and seeming to have limited hardware in relation to fi. the 735XT. Which is not clear when reading the consumer specs. So it is not very strange to be disapointed about the fact that the current flagship is near to a end of support status, at least regarding the SDK.

I do understand the feelings and frustrations. I am not picking a side. Having forked out a lot of money, one would expect it to be top notch for quite a while.

But something that is overlooked is the fact that the fenix3 hr is a fenix3 with...(drum roll)...optical hr. It still is a fenix3, and the fenix3 has been around for more than a year. So saying that it has been released under 5 months ago is not entirely true in terms of the basic fenix3 hardware. It is unfortunate that the fenix3 hr joined the party so late.

But like Jim already said, nothing will be broken or taken away.
For the planned 1.3 SDK there will still be a lot of new stuff that is being ported from the 2.1 SDK.
It definitely will have its shine for a bit longer! :D

I appreciate everyone's comments, and can understand why some are upset that certain products appear to be getting left behind.

Many current CIQ-compatible products (e.g. the fenix 3) were in development and released well ahead of Connect IQ version 2 (CIQ2). In fact, the fenix 3 debuted along side Connect IQ v1.0 at CES in January of 2015, and we're squeezing out every last bit we can to include as many CIQ features as possible. The decision to not bring some of these products up to CIQ2 often comes down to hardware capability. These are amazing little devices, but they aren't desktop PCs--instead of gigabytes or megabytes of memory to work with, some of these devices only have a few kilobytes. As the CIQ API grows, those new features take up space that simply isn't available on some of the earlier devices.

In response, we have brought as many features from CIQ2 into the version 1.3 virtual machine to provide as much of the new functionality as possible to existing devices and keep them relevant for as long as possible. We've also tried to make it easy for developers to build for any of the devices with a single SDK.

Admittedly, some of this is the result of Garmin's growth and adaptation to change in the wearables market. Let's face it--Connect IQ is a pretty new thing that some of our devices weren't explicitly designed around. We just didn't know how important CIQ would become for our customers, and weren't sure what its evolution would look like. Fortunately, Connect IQ has begun to mature and has become an integral part of the Garmin wearable (and other Garmin devices!) over the past 18 months.

I apologize to everyone that feels shorted by our inability to upgrade all of our devices to support CIQ2. We will continue to work to do what we can to provide the best tools to Connect IQ developers and offer valuable features to Garmin customers.

Bug:
Sys.println((1.0/3.0).format("%5.64f"));
Sys.println("testDEAD_BEEF");

result:

0.33333334326744080000000000000000000000000000000000000000000000Ff����testDEAD_BEEF

Code addresses the memory outside. Do not allow to do this.

Tried it from Eclipse but getting the following error:
Please set a signing key in the Connect IQ preferences.

What should I do with that?

Tried it from Eclipse but getting the following error:
Please set a signing key in the Connect IQ preferences.

What should I do with that?

Alright you have to generate a key yourself from the Connect IQ compiler preferences.

You need a signing key to sideload to a watch with a 1.3.x or 2.1.x VM. See the "app signing" sticky at the top of the forum.

This key is something you want to save off, as once you upload to the app store using it, you can only update that app if the same key is used. (today you can't build an iq with the 2.1.0 SDK, but I'd expect that will be allowed in the near future)

Code addresses the memory outside. Do not allow to do this.

Thanks for the report. We'll definitely get this fixed.

There's another piece to this whole thing - the <fitContributions> section in the .xml. That's the data that Garmin Connect uses to display fitcontrib data. The way I think it works, is that the definitions are included in the .iq, and when garmin connect gets a .fit with fitcontrib data, it gets the info from the app store as to how to display it.

So until 2.1 .iq files can be sent to the store, garmin connect won't do anything with the fitcontrib data.

There is a tool in the sdk to look at the data (monkeygraph), but it too needs a .iq. So for now, something like fittocsv is about it to test out fitcontrib.

I've created an app with settings and a fitcontributor and I'm testing it by side loading it on to my device. The device doesn't show my field in the summary at the end of the activity, I can't see anything about it in the Android app, and the Connect website isn't showing anything, so I'm not really sure if the data is being written to the FIT file. Where can I find this "fittocsv" app? I've looked in the SDK directory and googled around and I'm not really finding much. GPSBabel doesn't work with the newest version of FIT, so at this time there's really no way for me to see what's going on with the fitcontrib data.

fittocsv in in the fit SDK available at:

https://www.thisisant.com/developer/resources/software-tools/