SDK 6.2.0

I agree, but it's to align with the new Connect IQ System 6 https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/welcome-to-system-6

Edit: I am not seeing the size you do though. For me it shows 65.0 MB. I think the SDK manager crashed after loading before I could set it to be the default, so maybe for you it crashed earlier and you did not get the whole thing unpacked correctly. You may want to delete and try again:

I too am seeing 65mb and like you, the sdkmanager crashed before I could set 6.2.0 as the current SDK. I could after restarting the sdk manager.

Thanks! All is working great now. I deleted SDK 6 and reloaded and now it reports the correct size.

We're aware of the SDK Manager crash—it was observed yesterday while verifying things after our release and is only appears to only affect Linux and Windows. We'll get it fixed soon.

Hi Brandon:

After upgrade the SDK to 6.2.0，I found that the println doesn't work. Is it expected. Anyone else encounter the isse? Thanks.

In eclipse println runs well.

AlphaMonkeyC

What will the version number look like in 2024 q2 when there will be no system7?

6.12.0?

@_psx_

Thanks a lot for the info. I just built a vscode project and it show the println in fact. Thanks a lot!

@Brandon.ConnectIQ 

When I execute the command:

    monkeydo .\test.prg fr255

it seems that there is error as following and those cause the disconnect from the simulator. That's the reason I cannot print the output of "println". Others work well except this issu. Can you please help on it? Many thanks. Ｉrun it on windows powshell.

> monkeydo .\test.prg fr255
Exception in thread "Thread-0" java.lang.IllegalArgumentException: Invalid UUID string: 1C
at java.base/java.util.UUID.fromString1(UUID.java:280)
at java.base/java.util.UUID.fromString(UUID.java:258)
at com.garmin.connectiq.common.communication.channels.device.DeviceChannel.getUuid(DeviceChannel.java:151)
at com.garmin.connectiq.common.communication.channels.device.DeviceChannel.messageReceived(DeviceChannel.java:198)
at com.garmin.connectiq.common.communication.channels.shell.ShellChannelManager$1.sendNotifiction(ShellChannelManager.java:217)
at com.garmin.connectiq.common.communication.channels.shell.ShellChannelManager.notifyChannel(ShellChannelManager.java:194)
at com.garmin.connectiq.common.communication.channels.shell.ShellChannelManager.messageReceived(ShellChannelManager.java:214)
at com.garmin.connectiq.common.communication.shell.ShellProcess$1.sendNotification(ShellProcess.java:368)
at com.garmin.connectiq.common.communication.shell.ShellProcess.notifyListeners(ShellProcess.java:355)
at com.garmin.connectiq.common.communication.shell.ShellProcess.notifyInputReceived(ShellProcess.java:366)
at com.garmin.connectiq.common.communication.shell.ShellProcess.access$100(ShellProcess.java:14)
at com.garmin.connectiq.common.communication.shell.ShellProcess$ReaderThread.run(ShellProcess.java:41)

1) SDK 6.2.0 no longer allows IDs with start underscore - e.g. _myName, which I do with all Resources/Setting IDs. So there is a lot of work waiting because I have to change the IDs.
2) if I therefore do not (yet) work with 6.2.0 but stay with 4.x.x, the simulator crashes with datafields on all Edge x40 devices. (All older Edges work in the simulator).  VS Code.

Great!

I'm having several issues with the SDK 6.2.0.

The API documentation does not mention the new methods makeRviewTokenRequest and startUserReview.
In the online version it is available though. The online version has been generated on June 14th and the local version installed with the SDK has been generate on May 26th.

The new symbols can't be found by the compiler.

The drawBitmap2 method crashes in the simulator on many of the devices listed to already support the method. It works on the Fenix7 series though.

Is the new SDK ready for prime time?