Anyone with macos successfully running VSCode?

My VSCode environment is configured. I can build apps, but when I try and run them all I get is a blank Simulator window (yes, I have tried running twice - more than once).

My Eclipse environment is running flawlessly. Well, except for ERA where I have to delete and re-enter my developer credentials everytime (I logged a BUG for this some time ago).

VSCode is currently pointing to my Eclipse Workspace.

I am on macos v10.15.7

VSCode v1.50.1 (Connect IQ extension v0.1.2)

Connect IQ SDK v3.2.3

Java version 1.8.0_152

I'm particularly interested in anyone who has VSCode working AND has a different version of Java running on their MAC.

Thanks.

Top Replies

All Replies

0 Kyle.ConnectIQ over 4 years ago in reply to el34rob

el34rob, this is addressed in 0.1.4, but it requires a temporary modification of current-sdk.cfg located at ~/Library/Application Support/Garmin/ConnectIQ. See the announcement post for more details.

0 el34rob over 4 years ago in reply to Kyle.ConnectIQ

Thanks Kyle. Unfortunatley, still not working for me.. This is what I did:

- Update the extension in VSCode to 0.1.4 and restart VSCode

- Copy the connectiq-sdk-mac-3.2.3-2020-10-13-c14e609bd folder from its default location to a new folder containing no spaces.

- Then, update the current-sdk.cfg file in the original location to refer to the new location.

- As soon as I go to Verify configuration. I get the attached

- So I unset and reset the current SDK but I can see in the current-sdk.cfg file that it reverts back to the original location ("Application Support"). If I change the CFG file again I keep getting the above messages.

The App BUILD process still completes, but a Run App still presents a blank simulator window, but this time a message appears in VSCode saying "Unable to connect to simulator.".

Unfortunately, I cannot choose to install the SDK Manager in any other path - it seems to default using "Application Support" on macos.

+1 Kyle.ConnectIQ over 4 years ago in reply to el34rob

When you edit current-sdk.cfg, make sure there isn't trailing whitespace. I just edited this file with vim and it was tacking a \n at the end. If I use TextEdit it doesn't do this. Is it possible this is the issue?

Thanks for using the extension in its alpha state and helping us work out bugs. I just fixed this trailing whitespace issue so it'll be in our next release.

0 el34rob over 4 years ago in reply to Kyle.ConnectIQ

Thanks Kyle. Looks like that might have been the issue. I edited the current-sdk.cfg file using notepad++ in a windows VM and turned on showing control characters. None were visible when I saved it. Now My App runs, though I did have to "run twice" the first time (but only the first time).

0 el34rob over 4 years ago in reply to el34rob

I would like to change what I said about "run twice" only once. It seems I have to do that more than once, particularly if changing apps or devices, but I think that's already a known issue.

0 el34rob over 4 years ago in reply to el34rob

After the recent update to VS Code (1.51.0) and the MonkeyC extension (0.1.6) I no longer need to "run twice" and it might be my imagination, but it appears the simulator starts way faster than it used to from Eclipse. All I need now is the ability to update App settings and I'd be comfortable moving completely to VS Code. Great job.