MacOS Unable to connect to simulator.

I recently switch to a Mac and things generally work fine except after a few test runs in the simulator I eventually start getting "Unable to connect to simulator." errors and have to close the current project in VSCode and reopen it to get it working again.

This happened on Windows once in a while but on MacOS it doesn't take long before I have to reopen the project.

Any hints on how to avoid this?

Pete

Top Replies

Naz Avo 7 months ago +1

I'm having similar issue with "Unable to connect to simulator." error randomly happening after few builds. The only thing that helps to run the sim again is full machine restart, which is not the most…
flocsy🤠 7 months ago in reply to Naz Avo +1

I think it happens a lot more now, since I use SDK 7.1.0

All Replies

0 Brandon.ConnectIQ over 1 year ago

This is a known issue. I also work on a Mac and have been dealing with a similar problem. In my case, I always see the error on the first run of an app when the sim is not open, but re-running the app will launch the app without the error. Does closing and re-opening the simulator without closing and reopening the project in VS Code address the problem?

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

I have the opposite sequence. If the sim is not running it is launched correctly. A few subsequent runs will work but eventually I get the timeout connecting to sim error.

Sometimes killing the sim makes it work again and sometimes killing VSCode makes it work. So, I now kill both.

I switched to using the Windows version via Parallels. It works fine, just more cumbersome and slower...

0 Brandon.ConnectIQ over 1 year ago in reply to pstoppani

Hmm, okay. I'll update our ticket with your details. I'm not sure if what you're seeing has the same root cause as the already-reported issue so I want to make sure both cases are investigated.

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

I'm on MacOS 13.4.1. It's a new Mac so it has a fresh install of VS Code, SDK Manager, and Java. And I'm using SDK 6.4.0.

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

Let me know if/when there is a fix as I'd rather use the native MacOS tools rather than Windows+Parallels.

Thx, Pete

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

For grins, I timed how long it takes to export one of my apps:

MacOS : 2 min 35 sec

Win/Parallels: 6 min 30 sec

So, I'll be developing/debugging on Win and exporting on Mac...

Looking forward to a fix for the Mac.

0 jim_m_58 over 1 year ago in reply to pstoppani

The version of Java can make a huge differenc in the speack of exporting. With one, exporting an app took about 30 minutes, while another, less than 5. I currently have

openjdk version "17.0.2" 2022-01-18
OpenJDK Runtime Environment (build 17.0.2+8-86)
OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)

on my desktop

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

Also, Garmin Express crashes when I try to sync an Epix 2 Pro. . This was on the first time sync where it updates the maps. It takes a long time for it show an MB/s transfer rate and crashes almost immediately. Tried rebooting. Crashed again.

Back to Windows + Parallels...

0 jim_m_58 over 1 year ago in reply to pstoppani

Make sure you post in the Garmin Express for Mac Forum about this:

Garmin Express Mac - Mac/Windows Software - Garmin Forums

0 pstoppani over 1 year ago in reply to Brandon.ConnectIQ

I'm starting to see the same issue even in Win11 + Parallels. The only way to avoid this that I've found reliable is to close the sim between each app run.