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

1

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 in the IDE, same Mac)

I havent changed anything on my mac I can think of
IDE are all allowed to access local network in Privacy & Security > Local network

It doesnt appear to be Windows firewall blocking it
I’ve set to show notifications when it blocks & I never see one

Remote Debugger stub IS allowed through the firewall

2023 just doesnt even try to connect that I can find by looking in Little Snitch logs

ANY ideas ?

2

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.

3

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 !

4

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

5

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

6

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

7

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 ?
fails !

WTF …

8

sounds like something in your Appdata Folder is mismatching, maybe you clean all the related data there and retry?

9

: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 see WTF IS going on

10

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 - something remote debugging USED to do as well

I may switch to actually using branches in git then check those in & out and when things works the way I intend they I can commit changes to the main branch

crazy thing is remote debugging worked up until less than week ago
and now basically not at all and as far as I can tell nothing changed

11

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

12

I’ve seen weird things about networks.
Your story reminds me of something: I have two NAS devices at home, and if I try to copy a large file to NAS2 using the Finder, it’ll usually hang near the start and abort with an error -51. No problem with small files nor with large files to NAS1. I’ve concluded the NAS2 is somehow “overflowed” easily for whatever reason.
I’m saying this because your issue could be because some Xojo versions send “more data” and the network possibly couldn’t handle that, like mine. (all this is still a mystery, even on my side, so these are just wild guesses).

13

The entire problem is: the Xojo Code of their IDE and many other stuffs are totally buggy. So you may have problems to get rid of this except you use the newest version of Xojo. That’s their world. Incompatible, bug ignoring.

14

Not relevant but thanks anyway

CI/CD isnt the issue here
Its not a CODE issue

15

Yeah this is an IDE issue
I can even ssh into the remote stub on the remote machine
But the IDE itself basically never even tries

16

I’d love to chnage that
but I cant
So I may have to see if a newer version resolves this
However I’ve had mixed results doing that in trials
it will sometimes connect to the remote and sometimes not

17

2 posts were merged into an existing topic: Xojo Android