Client app built in Xojo 2023r1.1 Can open project in 2024r4.2 & 2023r1.1 - even both at the same time Both configured the same way as far as preferences (since they share them) 2024r4.2 connects to the Remote Debugger Stub 2.5 2023r1.1 doesnt (same stub on the same remote machine, same config …

I started having this issue in the last month or so. Restarting the Windows VM, or just suspending/resuming it usually clears it up. I haven’t done extensive testing, but it seems to occur after either running the Xojo IDE in the Windows VM or remote-debugging with a different Xojo version.

Not using a VM To an actual piece of hardware Weird thing is IF I create a new user account I can make it work In my existing account not at all It literally doesnt seem to even try Which is what made me think of Privacy & Security > Local network but its all enabled arg !

I think we had something like this going on too. Updating to a newer Xojo fixed it.

cough blech cough blech but yeah 2024r4.2 connects 2025r1.1 connects 2023r1.1 doesnt even try Except in a new user account and that works SO weird

Could it be you have a Little Snitch denying rule applying to 2023r1.1 and not the others?

Nope Checked all the rules And FWIW they seem to be applied by the bundle ID so they apply to every version of Xojo at the same time And it gets WEIRDER Ran 2024.4.2 Connects to remote machine Debug for a bit Stop the remote session made some changes in the code try & remote debug again ? …

[image] npalardy: Weird thing is IF I create a new user account I can make it work In my existing account not at all sounds like something in your Appdata Folder is mismatching, maybe you clean all the related data there and retry?

:man_shrugging: its sporadic works for a bit then doesnt and what worked then quits I might just have to put a copy on the remote machines & test that way since I can run the sources there then build on my normal machine I’m tempted to pointed the Xcode debugger at this & disassemble things to…

No joy here in Mudville So I’ve settled on an even dumber work around Actually install the version of Xojo + Plugins on the target machine and do debug runs there when / if I need to I can share the target PC’s drives to my Mac and clone source over there when / if needed Dumb but it works - som…

this is the best argument for an automated and working CI/CD pipeline :wink:

If Not Nil

Anyone have ANY ideas why this is the way it is?

Other

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled