Under Review
over 1 year ago

println doesn't work on 6.2.1 on console

After upgrade the SDK to 6.2.0/6.2.1, I found that the println doesn't work on console. I tried it on windows and linux console, neither works.

I just built a vscode project and it works. But I think the console should have worked.

This is the console log, I've update it on the discussion area, but I think I should paste it here for official report. Thanks.

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". Iruned 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)

Parents
  • It is not fixed for me using 6.3.0. I have the very latest Eclipse too. With the 4.1.2 CIQ IDE plugins.

    Could you have maybe done something else to fix it? For now I'm having to use VCS, which isn't as efficient for me at this point.

Comment
  • It is not fixed for me using 6.3.0. I have the very latest Eclipse too. With the 4.1.2 CIQ IDE plugins.

    Could you have maybe done something else to fix it? For now I'm having to use VCS, which isn't as efficient for me at this point.

Children