On an M1 Mac, I have the latest (2025R2.1) Remote Debugger running. When from my M4 Mac I run the app on the M1 remote, it transfers, launches the app and then warns it cannot connect and quits the app. This happens on both 15.6.1 and Tahoe public beta. Remote debugging on another, older intel Mac (Sonoma 14.7) remote debugging works fine, so it’s not my IDE M4 that’s blocking communication. Does anyone else have this issue or suggestions on how to fix? I tried removing debugger, flushing cash, rebooting and all the usual suspects to no avail.
Check and see if the firewall is enabled on the M1 and if it is, that your app is allowed in the bypass list. The app you’re building must be allowed to connect back to the IDE over the network.
Another thing to try is running the console debugger stub. That shows the communications between the programs and might give you an insight.
oh, and make sure the stub you’re using is ARM or Universal. The older Intel-only stubs may not tell the IDE the correct target platform info.
Thanks, but firewall is off on both macs
I tried getting the console debugger but ran into some issues there too. I have a feeling it might have to do with the tightened security in 15.6.1 as the debugger ran fine before this version.
Do we know if the Remote Debugger Stub does ad-hoc signing on the destination Mac?
You are not alone. But not big issue for me, from Mac to Windows or Linux it is working fine. I also guess some security measures on macos are the problem.
The IDE does the signing, but if that were the problem, I’d expect it to happen for every machine he’s debugging to.
Could be that the app needs the local networking entitlement though.
I found a temporary workaround. After starting the Remote debugging and you get the error message Remote Debugger cannot connect to the IDE, click ok on that error and then manually launch the app.debug. Then it does launch. To me, this is a clear indication the issue is within Remote debugger not getting the right permissions or something.
1 Like
Oh that makes it sound like the issue that keeps coming up where macOS denies local connections for an inexplicable reason at launch.
1 Like
That’s awesome, thanks for sharing. I can confirm this works 
I assume you can’t still step through code like this….
Actually after you manually launch the debug app, it runs just like always and you can use it to debug just like in earlier MacOS versions
Is there a feedback ticket open?
For me, remote debugging Parallels Windows VMs from a Mac with Tahoe has become quite unstable. Often the remote debugger will find the connection only after several attempts (while the good news is that the error usually pops up immediately), but much more severely Xojo often unexpectedly quits (or crashes without notice) when I start a remote debug session.
I can’t get remote debugging to Windows VMs to work at all on Tahoe. Debugger just fails to connect to the stub.
Also after several attempts? Usually works for me on the 5th at max.
- Shutdown the VM
- Rebooted the Mac
- Restarted the VM and Remote Debugger Stub
- Opened the IDE with a blank project
- Run Remotely
Now works. Sigh.
1 Like
Does the error appear after a timeout or immediately when you try to run?