Acknowledged
5 months ago

Simulator does not work with the most basic example setup from the docs

Trying to develop for the Venu3, but new to Connect IQ platform
Can't get a basic developing setup to work by following the tutorials.

Creating a project all seems to go fine, but running a file like MetronomeApp.mc by pressing F5 will via Run > Run without Debugger launches the Simulator but simply gives me a gray screen with 0 interaction options. 

Weirdly enough, when I sideload the app onto my watch it does seem to work which makes it even stranger.

Launching the simulator does give me an error in VSCode about being 'Unable to connect to the simulator'

Sadly a lot of the documentation seems outdated or otherwise suggests things work differently from how it actually does. (no .vscode folder is created automatically, no screens in the simulator, etc).

Details about my setup:

- host on Windows 11

- VS Code version 1.89.1

- Latest version of the Monkey C extension

- Connect IQ SDK 7.1.1 installed

- All Watches/Wearables as devices installed

- Running verify installation in vscode via the command prompt works fine

- Running Java jre1.8

- Command that is used to launch the simulator: 

c:\Program Files\Java\jre-1.8\bin\java.exe -Xms1g -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar c:\Users\...\Garmin\ConnectIQ\Sdks\connectiq-sdk-win-7.1.1-2024-04-17-66d0159ae\bin\monkeybrains.jar -o bin\Metronome.prg -f c:\Users...\Metronome\monkey.jungle -y c:\...\developer_key -d venu3_sim -w

Mantsje
  • 2 months ago in reply to Brad.ConnectIQ

    Sadly I'm at wits end trying to get this to work.

    Deleted the Sim-$username file

    Booted into Safe mode

    downloaded SDK 7.3, 7.2, 6.4

    copied the SDK to /tmp and executing the simulator there

    -- using either ./bin/connectiq or

    -- ./bin/ConnectIq.app/bin/macOs/simulator

    then trying to get VSCode to run (with and w/o debugging) still results in unable to connect to simulator

    doing it on th command line also have the same issue (using monkey x.prg fenix5xplus)

    Also upgraded to latest Sonoma 14.7 (was 14.4)

    Rebooted multiple times

    VSCode - 1.9

     java --version

    openjdk 21.0.4 2024-07-16 LTS

    OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS)

    OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode)

    Apple Silicon Mac

  • 4 months ago

    Same issue for me, i'm trying to deal with a simple DataField sample (fresh sample created) and the Debug Console just show:

    Unable to connect to simulator.

    No more feedback or crashing logs

  • 5 months ago

    Try to delete the Garmin folder from the temp folder (C:\Users\<username>\AppData\Local\Temp\com.garmin.connectiq\). If the problem still persists, try to delete the SDK and reinstall it or try with another SDK version.

  • 5 months ago in reply to Brad.ConnectIQ

    Hi Brad,

    There is definitely no simulators running. Cancelling the "Run" through VSCode, rebooting and then retrying on a freshly booted system, restarting VSCode, killing the simulator.exe through task manager are all ways I have tried but to no avail. 

    I don't see how running the simulator from the Roaming folder it is installed is supposed to change things? It also does not seem to work.

    In all cases the simulator boots to an empty gray screen in which I can perform `File > {Kill Device, View Memory, View Profiler, Edit Persisten Storage, Delete All Apps, Quit}` 
    All other options are grayed out. None of the options show any information. The watch UI is never loaded.

    (I got it to work on my Linux boot so I have an idea of what it should look like I guess)

    If you need any more information let me know

  • 5 months ago

    Ensure that no device simulator is running. If the simulator hangs (ie; Debugger paused, or all of the menu options are greyed out), kill the simulator. If the issue is still persisting, check to see if the simulator can be launched manually from the SDK location. If you have to attempt the final option please let me know about it and I'll escalate the issue to be looked into further.
    Thanks!