Connect IQ 2.1.3 SDK Available!

Eclipse 2.1.4 Plug-in

For those of you that have installed the 2.1.3 SDK and the 2.1.3 plug-in during the past day or so, we've published an updated to the plug-in, version 2.1.4. This plug-in release includes a small fix for an issue that prevented a target SDK selection when building or simulating for Oregon 7xx and Rino 7xx devices.

You can get the latest plug-in update by visiting the Help menu in Eclipse, and choosing Check for Updates.

It would be really valuable if you could cut and paste the change log here.

The link you included was basically just an ad for the Chronos, with no actually information. The only way we have to find out what's fixed/new is to install the update (that I can see at least).

Thanks.

When you download the sdk, the change log is in the readme file in the sdk directory (also the changes for the prior versions, so you can catch up if you skipped one) You can download a new SDK and still use an older one, but you probably want to use the new one.

When you download the sdk, the change log is in the readme file in the sdk directory (also the changes for the prior versions, so you can catch up if you skipped one) You can download a new SDK and still use an older one, but you probably want to use the new one.

Yep, know that.

But it would be nice if the actual changes were listed in the announcement post for those who aren't updating right now for whatever reason (I won't be until tonight but would still like to know). Somewhat of a trivial cut and paste really.

Here you go...

v2.1.3

General Changes:

• Add support for fēnix Chronos.
  
• Add ability to target specific SDK version when building for a device.
  
• Fix a crash in image requests on 2.1 devices.
  
• Cancel pending image and JSON requests when an app is closed.
  
• Fix a bug where max cadence overwrites average.
  
• Fix a bug where formatted strings weren’t properly terminated.
  
• Fix a bug where settings files were being deleted for new apps loaded via Garmin Express.
  
• Fix unintialized variable in input sample project.
  
• Add missing device support for some sample projects.
  

Compiler Changes

• Add -s option to target a specific SDK version when compiling. Example uses of this would be “-s 2.1.1” or “-s 1.3.1”.
  

Simulator Changes

• Fix a bug where the status bar truncates memory information.
  
• Fix a bug in handling of transparency for some devices.
  

Known Issues:

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

Is there an easy way to find out which part of a watchface causes the to many arguments error?
If I use 2.1.2 it´s working, with 2.1.3 not.

I already read this thread, but didn´t help.
https://forums.garmin.com/showthread.php?358985-Too-Many-Arguments-Error

Find out what function call is getting the wrong number of arguments, then fix. If you don't get a stack, the easiest way to do this is to....

• Sprinkle Sys.println() calls throughout your code
  
• Run it
  
• Note the last line that was output.
  
• Eliminate all but the last Sys.println() that completed before the error.
  
• Add more Sys.println() calls after the one that remains.
  
• Go to step 2.
  

Travis

found the Problem

function onLayout(state)

this was missing.
Don´t know why this is necessary

Now I have an other Problem, maybe caused on a fault in the SDK.

If I chosse min SDK Version 2.1 in my watchface properties, the fenix 3/.. are not available anymore.
I´m wondering about that, because in the documentation I found this in the point SensorHistory.

Module: Toybox::SensorHistory

Overview

The SensorHistory module contains the interface for SensorHistory

Since:

2.1.0

Supported Devices:

Forerunner 235/735xt/920xt

fenix 3/HR

D2 Bravo/Titanium

Vivoactive HR



Maybe I´m wrong, but for my it sounds like, I must select the SDK 2.1 to use the SensorHistory feature?
But my Fenix 3 is not supported in Eclipse if I do that.

The SensorHistory and devices was something I noted a while back, with the note about 2.1.x and the f3 and f3hr which are 1.3.x devices.

What you can try is set the min CIQ to 1.3 and the f3 will show again..

In the simulator SH is always available as well as the 4 calls (getHeartRateHistory(), etc). You may want to just build something simple for the f3 that checks that SensorHistory is available:

var hasSH=(Toybox has :SensorHistory) ? true : false;


and display the results. If it's false, it's not available on the actual device. If it's true, you may want to check which of the histories is available:
using Toybox.SensorHistory as SH;
.
.
.
var hasHRH=(SH has :getHeartRateHistory) ? true : false; //for example