Connect IQ 1.2.1 SDK Available!

It's official! The Connect IQ version 1.2.0 SDK beta has attained it's final form, and is now available for download as the 1.2.1 SDK!

There are two ways to get your hands on it:

Download from out developer site at http://developer.garmin.com/connect-iq/sdk/
Use the SDK Manager under theConnect IQ menu in Eclipse

Be sure to update the Connect IQ plug-in in Eclipse to v1.2.1, by clicking on the Help menu and choosing Check for Updates. If you have trouble with this, review the configuration described in the Getting Started section of our Programmer's Guide.

Lastly, get the latest device firmware updates for your devices to ensure they have full support for all of the great Connect IQ 1.2.1 features!

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) :(

Updating to 1.2.1 my datafield is down to 9.0 KB with file playback. Muy bueno!! Great work, thanks :)

PatFelstead over 9 years ago

Thanks Garmin - my data field has gone from 14.9KB and out of memory errors down to 9.8KB and runs perfectly once again!

teadriven over 9 years ago

Device: VA running v3.30 firmware.

When testing out the new settings capabilities via the Connect android application it causes the watchface to crash and switch to the default one. Having set up a log for my watchface it is showing this:

UnexpectedTypeException: Expected Number/Float/Long/Double, given Number/String
initialize in d:\Projects\Git\reveal\TVM\api\Ant.mb:124

If I force an update of the settings again I can get my watchface back (usually by swiping to the widgets and then back again). Configuring the settings works perfectly via the simulator.

The CIQ_LOG.txt is also showing this:

ERROR: Unhandled Exception
DETAILS: Failed invoking <symbol>
STORE_ID: A1C3751265CF46BCB95761865106E087

teadriven over 9 years ago

I've figured out the conditions under which the aforementioned crash is occurring. My settings consists of

Two boolean switches
A list of options

If I change either (or both) of the switches and press "Done" the watchface will crash.
If I choose an option from the list it is fine.
If I wish to toggle a switch, as long as I choose an option from the list (it can be the same option as currently selected) then it will apply without issue.

I believe that the settings are being submitted to the watch with an invalid value for the list in the case that the option has not been changed.

Stanislav.Bures over 9 years ago

compiler exit code 143

Have anybody the same problem on MAC? I tried on two different MAC computers, but there is same problem. On windows PC it works. :(

Former Member over 9 years ago

I've figured out the conditions under which the aforementioned crash is occurring. My settings consists of

Two boolean switches
A list of options

If I change either (or both) of the switches and press "Done" the watchface will crash.
If I choose an option from the list it is fine.
If I wish to toggle a switch, as long as I choose an option from the list (it can be the same option as currently selected) then it will apply without issue.

I believe that the settings are being submitted to the watch with an invalid value for the list in the case that the option has not been changed.

The settings in GCM sometimes return a String instead of a Number. If you perform a toNumber() on the setting, it should work. Just to be safe, you could also check it's not null or an empty string.

Former Member over 9 years ago

The settings in GCM sometimes return a String instead of a Number. If you perform a toNumber() on the setting, it should work. Just to be safe, you could also check it's not null or an empty string.

To clarify, this is a bug in GCM that should get corrected, but the workaround as suggested by TeunMo should fix things and protect you from any future issues or corrupted data.

lcj2 over 9 years ago

Have anybody the same problem on MAC? I tried on two different MAC computers, but there is same problem. On windows PC it works. :(

I did not have the same issue. Did you also update the Eclipse plug-in as well as the SDK? I do have issues with the configuration tool in Eclipse now crashing the simulator which seems to be resolved by exiting out or Eclipse and loading everything thing again.

Brandon.ConnectIQ over 9 years ago

The compiler returning an unknown exit code is an issue that intermittently affects both Mac and Windows, and we're aware of the issue. We've been investigating, but haven't found a good explanation for why this occurs. The current work around is to copy the build command from the console in Eclipse and run it at the command prompt. You can read more about it in this thread:

https://forums.garmin.com/showthread.php?323303-Export-to-store-Can-t-build-package

teadriven over 9 years ago

To clarify, this is a bug in GCM that should get corrected, but the workaround as suggested by TeunMo should fix things and protect you from any future issues or corrupted data.

Thank you TeunMo and Brian, unfortunately two releases later and this did not resolve the issue.
It still crashes unless I explicitly select an option from the list, I get the feeling that it is crashing before it even attempts to retrieve the property.