Can't get SDK 4.0.10 and can't log back into SDK manager.

I just saw the announcement for support for the new Instinct watches and began updating through the SDK manager.

The device definitions came in without a problem.

When I tried to build I got an error since I hadn't downloaded SDK 4.0.10 so I went back into SDK manager and 4.0.10 did not appear in the list of available versions.

Having had trouble recently with the SDK manager and seeing those problems resolved by logging out and back in I decided to try that.

Now my attempts at logging back in to the SDK manager are being rejected.

Can anyone help ?

Top Replies

markw65 over 4 years ago +1

I'll just note that its not just the order thats off. I just did an install on a new machine, and when I opened the sdk manager it auto-downloaded 4.0.9 and prompted me to select that as the default. So…
jim_m_58 over 4 years ago in reply to flowstate +1

See https://forums.garmin.com/developer/connect-iq/f/discussion/285506/the-instinct2-s-require-vs-code-to-run-the-sim/1375728#1375728

Kyle posted the sort order will be fixed in the next version of the…

All Replies

0 Jeff over 4 years ago

I can now log back in (?) but SDK 4.0.10 still is not listed.

0 jim_m_58 over 4 years ago in reply to Jeff

The order is odd. It's between 4.0.1 and 4.0.2

0 Jeff over 4 years ago in reply to jim_m_58

I just went to the SDK download page and it says 4.0.10 as well.

I did the download for Windows and installed it.

There's no newer SDK. I'm currently using 4.0.9.

The only higher numbered (older) SDK shown is 4.1.0 Beta 1

So.... it looks like the device packages for the new Instincts are available but the required SDK is not, or there's some kind of numbering problem.

One more issue that I've been seeing since I loaded SDK 4.0.9 and some new devices... All of the devices in the device list are marked New though I've been building for most of them for a while. It would be nice if the New indicator marked devices that actually are new to my setup. Is there a way to correct that ?

Thanks

0 jim_m_58 over 4 years ago in reply to Jeff

Like I said the order in the SDK Manager is odd:

0 Jeff over 4 years ago in reply to jim_m_58

Ahhh.... not listed by date.

I now have 4.0.10 loaded and selected as the SDK in use.

When I attempt to create a Run configuration for the Instinct 2, the SDK selection comes up blank. No options available.

Any thoughts ?

0 jim_m_58 over 4 years ago in reply to Jeff

You have to use VS Code. See https://forums.garmin.com/developer/connect-iq/f/discussion/285506/the-instinct2-s-require-vs-code-to-run-the-sim

0 Jeff over 4 years ago in reply to jim_m_58

Thanks Jim.

Not good news to me. I don't need another learning curve to climb while I'm trying to do useful work.

Any idea if there is some way that I'll be able to know in the future whether a device is supported in Eclipse ?

Having the device definitions show up in the SDK manager and download is quite misleading if I can't build for those devices.

0 markw65 over 4 years ago

I'll just note that its not just the order thats off. I just did an install on a new machine, and when I opened the sdk manager it auto-downloaded 4.0.9 and prompted me to select that as the default. So the sdk manager itself thinks that 4.0.9 is the latest. I guess it sorts in ascii order for both display purposes, and to determine the latest sdk...

0 flowstate over 4 years ago in reply to markw65

markw65 said:
I guess it sorts in ascii order for both display purposes, and to determine the latest sdk...

Yep it's typical Garmin. I noticed this a while ago and I wanted to file a bug report but I guess I forgot about it.

(Nitpick: it's lexicographical/dictionary sort order where individual characters are compared, not necessarily "ASCII" sort order. For example, a standard unicode sort will produce the same results.)

What's needed here is a "natural" sort algorithm which attempts to isolate numeric sub-sequences in strings. (It's worth nothing that none of the natural sort algorithms are perfect afaik -- as in they won't handle every conceivable case -- but there's definitely natural sort algorithms that will handle this case.)

I've opened a bug report now:

forums.garmin.com/.../sdk-manager-sorts-4-0-10-incorrectly-between-4-0-1-and-4-0-2-instead-of-after-4-0-9

0 jim_m_58 over 4 years ago in reply to flowstate

See https://forums.garmin.com/developer/connect-iq/f/discussion/285506/the-instinct2-s-require-vs-code-to-run-the-sim/1375728#1375728

Kyle posted the sort order will be fixed in the next version of the SDK Manager..