Connect IQ 1.2.0 SDK beta!

This morning we released a public beta of the 1.2.0 Connect IQ SDK! The beta SDK will allow developers to get their hands on the fun stuff we've been putting together lately, and gives everyone a chance to update their apps to take advantage of these new features. In addition to the SDK beta, there are also beta firmware releases for all current Connect IQ devices to include support for the 1.2.0 SDK. You can read about the details, as well as find links to the SDK and firmware downloads, over on our developer blog:

http://developer.garmin.com/index.php/blog/post/announcing-connect-iq-1.2

Just a couple of notes:

We've temporarily disabled the ability to build app packages via the App Export Wizard (which creates .iq files) to avoid 1.2.0 beta apps from making their way to the Connect IQ app store until we are out of beta. Developers will be able to create PRG files with the Build for Device Wizard, however, which can be side loaded for testing on devices. If you're planning any updates to apps that are on the store, and the updates don't require 1.2.0 SDK features, build with the 1.1.4 SDK so you'll be able to publish those updates to the app store.
If you plan on trying out the 1.2.0 SDK beta, please be sure update your Eclipse plug-in to version 1.2.0 by clicking the Help > Check for Updates menu item.

Nikeow over 9 years ago

It's late here and I prob missed or don't understand it. The objectstore - how does it function for a datafield to store configurations such as being able to select which fields can be used? Or what about the Visual HR Zones datafield? The object store, currently is only able to do simple things such as define what are the HR Zones? Just ability to out a number to an existing zone definition? (I noted in the example that the default always be there, the. Changes done in the GCM)

Tell me please that there more than that?

The 'picker' seems interesting but too late for me to read more into it.

Also - I don't fancy loading my watch w the beta FW. So... What are the options? Or I guess the. Plan is to roll to existing stable FW branches by mid October?

Thanks for the insights.

bwd1 over 9 years ago

Great work, thanks. The new features look really good.

Using 1.1.4 my data field was 12.3KB and ran fine on the simulator. Updating to 1.2.0 changes it to 13.2KB which then gives out of memory errors (14.6KB with file playback) :(

Former Member over 9 years ago

Cannot get the simulator starting

Hi,

On macosx i can't get the simulator starting with this SDK version. Is this a known issue?

julienvm over 9 years ago

Thanks Garmin for investing in the development of Connect IQ.

Kyle.ConnectIQ over 9 years ago

Hi,

On macosx i can't get the simulator starting with this SDK version. Is this a known issue?

Are you getting an error message when you try to open it? How are you trying to open it? Via the plug-in or via Finder?

Former Member over 9 years ago

Are you getting an error message when you try to open it? How are you trying to open it? Via the plug-in or via Finder?

Via the eclipse plugin I am not getting any error. From Finder I get an error telling the Connect IQ app is not a valid app.

Is also have this with sdk version 1.1.4.sdk version 1.1.3 does not have this problem

HermoT over 9 years ago

Congratulations!!

Well done on the latest release Garmin!

Just had a look at the Picker sample. Can't wait to start playing with it!

HermoT over 9 years ago

It's late here and I prob missed or don't understand it. The objectstore - how does it function for a datafield to store configurations such as being able to select which fields can be used? Or what about the Visual HR Zones datafield? The object store, currently is only able to do simple things such as define what are the HR Zones? Just ability to out a number to an existing zone definition? (I noted in the example that the default always be there, the. Changes done in the GCM)

Tell me please that there more than that?

The 'picker' seems interesting but too late for me to read more into it.

Also - I don't fancy loading my watch w the beta FW. So... What are the options? Or I guess the. Plan is to roll to existing stable FW branches by mid October?

Thanks for the insights.

I also have a late night now, but think the Picker is where the power of user configurability lies that we all have been waiting for, right?

Brandon.ConnectIQ over 9 years ago

Every time we add APIs to Connect IQ, the code space required grows a little bit and cuts into available memory, so that's likely what's eating up that extra K of memory under 1.2.0. Data fields have very little memory to work within right now, as you know, but thing should improve in future devices as our hardware evolves. Apologies for the trouble!

Using 1.1.4 my data field was 12.3KB and ran fine on the simulator. Updating to 1.2.0 changes it to 13.2KB which then gives out of memory errors (14.6KB with file playback) :(

Nikeow over 9 years ago

Hi Brandon

I don't think this is acceptable from Garmin to be doing this. 1.1.3 -> 1.1.4 already ate up memory - which we got was a bug but seems like it's a "feature". 1.2 further eats into memory and with 16kb for a datafield, going to 13.5kb is the max ceiling before out of memory happens.

fix the memory usage please. Or do like what done for the Epix where it is increased to 1024kb (per the release notes)