Xojo 2026 running prior code in debugger

General
1

All of a sudden Xojo v2026R1 is “stuck” on an earlier version of code when I try to run it in the debugger. It saves changes to the code when I look at it, but when it runs it clearly isn’t executing the latest version of the code even though that is what is appearing in the debugger at a breakpoint. I have tried restarting the IDE, updating the IDE to v2026R1.1, rebuilding/recompiling the app (not just running it in the IDE) and rebooting my MacBook Pro (M3 Max) running MacOS Tahoe 26.4.1.
After Google search, I am running the IDE on my main hard drive (not a network drive or partition). I have seen possible fixes of deleting the .uistate file (can’t find any .uistate file despite repeated searches including for hidden or invisible files) and I also can’t find a Debug(AppName) folder to delete. I’ve used Xojo for years and have never had this happen before.

1 Like
2

Remove it and install the lasy version (1.1) ?…

3

Try clearing cache in Xojo preferences.
Not on my macOS right now but I think it is under preferences → build setting
Worth a try

4

It could be the debug executable is not being deleted between runs. I’ve certainly had that happen when the project is on a network drive.

The debugger would usually fail to start in that case.

5

I have tried multiple combinations of the following with no success:

  • Upgrade to latest version v2026R1.1

    Restart IDE

    Reboot laptop

    Change code and resave

    Change build settings and resave

    Change MacOS Sign to None in build settings and resave

    Rebuild the program

    Click Run in IDE to run in the debugger while holding down the Option key to force recompile

    Clear caches in Settings → Building

    Remove all remote debugging hosts in Settings → Debugging

6

Not sure what to tell you, but some other things to test:

  • Save your project to a different folder
  • Save your project to other format (binary, xml, text)
  • File → Collect Project Items…
  • DirtyAllProjectItems

I hope you can find the problem. What format are you using?

7

I had an issue like this about 12 years ago where i could see the debugger stepping through the wrong code. I could never find the trigger to make it happen, but the solution was touching a certain module that caused something to recompile correctly.

Maybe go through all your code and make 1 small change to each module and see if that helps.

The problem went away a long time ago. Just mentioning it as it was similar and no reboots etc could fix it.

8

I’ve tried saving to a different folder, saving as a different format, collecting project items, dirtyAllProjectItems, and changing a line of code in every module. I appreciate all the suggestions, but nothing has worked.

9

I’ve never seen this, so I’ll go for the simplest explanation since we don’t have any real information to work from:

Are you sure you’re not hitting similar code to what you’ve changed and going down a different codepath than expected? Say, two modules, each with a DoX(y as String) as String function? Or a subclass where your code is running into the superclass method rather than a subclass’s method?

10

Charles:

take a break from this trouble.

If you need to continue, create a new project and add features there, you will incorporate that later.

In some days (say on Monday), make a cold boot, fire Xojo only, and check how is the situation with a fresh eye.
If the trouble is still there, start a debug session and maybe you will be able to find what’s wrong now.

PS: I have time and I use that technic often with success (but my memory does not works fine, so that help me).

11

May add a new user to macos and try with this user on a fresh duplicated text project.