ev3dev
MacOS Sequoia Support
Describe the bug Ev3 can be detected, but not connected to, on MacOS Sequoia. This fix required additional OS configuration. See Additional Context below.
To Reproduce Follow normal steps to connect to device. It is visible in the top bar in VSCode. An error with EHOSTUNREACH is listed.
Expected behavior A successful connection as normally seen in prior versions of MacOS, Linux, and Windows.
Desktop: MacOS Sequoia (15.0+)
Additional context Discovered a fix, which I recommend go into the troubleshooting section in the Wiki. Sequoia has added a "Local Network Access" limitation and VS Code is not automatically included. To address, open Settings->Privacy and Security->Local Network then toggle the slider next to Visual Studio Code to "on". Another possibility is to see about asking for that permission, but I'm not sure how to do so. As of writing this, very little documentation appears to be available.
It looks like this affects lots of other VS Code users for all sorts of things. So hopefully it will get fixed in VS Code. https://github.com/microsoft/vscode/issues/228862
I totally agree, and that's a good reference. Maybe worth mentioning in the Troubleshooting Wiki? I certainly don't think this is an ev3dev browser problem, but it might be helpful.
Can you share a screenshot of the settings so I. can put it on the wiki? I haven't updated to Sequoia yet.
UPDATE: I was able to work around this by switching the VM's Network mode from Bridged to Shared. Once I did that everything "just worked". It's not my preferred network mode but in a pinch it got me out of trouble.
Also, note that this didn't just affect UTM, it is affecting the latest VMware fusion build as well. While it could be an issue on Apple's end, I do wonder if it's got more to do with apps not all following the security model to a tee, and that Sequoia happened to be the point of no return.
It reminds me of past major tech cutovers on macOS and other apps that have nothing to do with UTM! In cases like this it can be tough to know and things are not always as they appear. Thoughts welcomed.
x-post: UTM Issue 6692
I upgraded my VS Code and don't see it listed under Privacy & Security > Local Network at all. Even after a reboot and numerous restarts of macOS and VS Code. I'm on Sequoia 15.0.1.
Maybe this comment is helpful? Although I would suggest to backup .vscode instead of deleting it.
https://github.com/microsoft/vscode/issues/228862#issuecomment-2395509928
In my case, I was able to resolve the issue by ensuring that the VMs were on the same subnet as my laptop (which gets its IP from the router via DHCP). To do this, I changed my router's default DHCP range to match the range of the VMs I had already created. I also used bridge mode in UTM, and everything worked fine with macOS 15.0.1.
If you don't have existing VMs, you can just make sure to create them on the same subnet as your Mac from the start.
The fix here saved my day after lots of failed troubleshooting and searches for a fix! It should definitely be mentioned in the troubleshooting document.
