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.

jim_m_58 over 9 years ago

Is there possibilities to have all the menu stuffs to be offloaded to the Garmin express or such?

"User Settings" in 1.2.0 doesn't allow menus, but does include things like lists and specific data, where the user can use GCM or GE to define how CIQ stuff on the watch works.

It might not eliminate all you need to do from your app, but you may be able to reduce what you do in your app.

Synning over 9 years ago

I noticed that the new beta firmware for Fenix 3 had support for Connect IQ SDK 1.2.1. Any input on when this will be out, and what are the updates? Would be great if you could provide more transparency into future plans.

jim_m_58 over 9 years ago

Are you sure it has 1.2.1? Because the 1.2.0 SDK and VM hasn't been released yet (still beta).

I don't doubt there will be a "1.2.1", as per the developer blog there is a process. But I wouldn't expect anything big...

A Connect IQ micro release (x.y.Z) can have: :

Bug fixes
New APIs to support bug fixes
Add support for a new product to the SDK

http://developer.garmin.com/index.php/blog/post/looking-forward-connect-iq-release-schedule

Synning over 9 years ago

Are you sure it has 1.2.1? Because the 1.2.0 SDK and VM hasn't been released yet (still beta).

I don't doubt there will be a "1.2.1", as per the developer blog there is a process. But I wouldn't expect anything big...

A Connect IQ micro release (x.y.Z) can have: : Bug fixes New APIs to support bug fixes Add support for a new product to the SDK

http://developer.garmin.com/index.php/blog/post/looking-forward-connect-iq-release-schedule

This is it, clearly states 1.2.1:

https://forums.garmin.com/showthread.php?329508-Fenix-3-6-11-Beta-Release

BRIANBAN over 9 years ago

Datafield memory issues

I finally found some time and recompiled with an outdated SDK to work around later SDK out of memory issues on the Vivoactive. This works fine, until you try to upload the new build to the Garmin app store - when you are greeted with this:

So you can't upload app compiled with an earlier SDK, and once a new SDK is released you can't then update any data fields that need the original memory size.

Cmon guys.

Former Member over 9 years ago

Are you sure it has 1.2.1? Because the 1.2.0 SDK and VM hasn't been released yet (still beta).

I don't doubt there will be a "1.2.1", as per the developer blog there is a process. But I wouldn't expect anything big...

We won't reuse the 1.2.0 release version for a non-beta release, so the official SDK release will be one of the next versions. (e.g. 1.2.1, 1.2.2...) I'm not sure if the impending 1.2.1 is the official release, or another round of beta. Either way, I am pretty sure it only includes beta bug fixes.

Former Member over 9 years ago

I finally found some time and recompiled with an outdated SDK to work around later SDK out of memory issues on the Vivoactive. This works fine, until you try to upload the new build to the Garmin app store - when you are greeted with this:

So you can't upload app compiled with an earlier SDK, and once a new SDK is released you can't then update any data fields that need the original memory size.

Cmon guys.

The increases in memory consumption in newer versions is controlled by the version of the VM that is running on the device, not the version of the VM you compiled your app with, so you can't just compile with an old version of the VM to make it work.

We hope to have some improvements related to this issue soon.

Nikeow over 9 years ago

simce on the topic of memory consumption, is there any work being done on optimizing the menu system?
It takes far too much (precious) memory to transverse the menu system currently to do initial setup.

jim_m_58 over 9 years ago

simce on the topic of memory consumption, is there any work being done on optimizing the menu system?
It takes far too much (precious) memory to transverse the menu system currently to do initial setup.

This thread is about the 1.2.0 SDK, and again suggest you look into "User settings" from GE/GCM to simplify the menus you need. That is a way to reduce menu subsystem memory you need and can be done today!

BRIANBAN over 9 years ago

The increases in memory consumption in newer versions is controlled by the version of the VM that is running on the device, not the version of the VM you compiled your app with, so you can't just compile with an old version of the VM to make it work.

We hope to have some improvements related to this issue soon.

Great thank you.

I think it would be worth posting this update in a more visible post too, as the advice I received from forum members earlier was that memory consumption is based on the version of the API that you build against.