I’m not currently using any macOS 11+ features in my app, and for a little while, until some users update their Macs to macOS 11+, how can I compile with Xojo 2025R3 to be compatible with macOS 10.15?
No, you can still use 2025r2.1 for that. R3 uses SDK 26, which is not compatible with macOS less than 11.0.
Even using UI compatibility mode?
(I haven’t played with that yet)
That only modifies the UI, not the entire SDK. The only way of supporting 10.x is to use 2025r2.1 or earlier.
That is sad for all my clients with good old mac.
With 2025r3, at least with my projects, I am still able to cheat down to Mojave by setting the minimum system in App Wrapper. I had previously done this to avoid dropping High Sierra. This is working well for me, but I realize that I am on my own here (and I do have to ask myself whether its really necessary.) 
See my answer to Ian, but understand that you would be in unsupported territory here.
UI Compatibility is for “forward” compatibility, not backward. It allows you to hedge your bets when running your existing projects on Tahoe, till you are happy with how they look with the new UI. It is also a temporary (!) feature from Apple.
It will depend on what you’re using. The IDE has already crashed when run on a 10.x OS (which has the problem that the minOS is set too low).
1 Like
Yes, I can confirm that remote-debugging to these targets is not a thing.
Just to clarify, the IDE has a minOS version of 10.13 and has been shown to crash when run there.
Application created by the IDE (including in debug mode) have the correct minimum OS version of 11.
That low? I thought that it had been 10.14 for years. As to built apps, I acknowledge that (using App Wrapper) I’m getting away with a hack
It’s a mistake, there’s a ticket, and hopefully they will take two seconds to fix it for a R3.1
1 Like
I have an automated sh script to compile and publish on our server instead of app wrapper. I will try to modify the .plist in that script
Thanks for the idea
You’re welcome. I suppose it may be useful for important customers on legacy systems. But remind them that they’re on legacy systems, which limits your support ability. As for me, I’m rather on a lark and will drop it eventually.
I’m slowly switching old mac client to Ubuntu… an 15 year old Mac runs smoothly and my app works perfectly on Ubuntu 24 and 25
Just for clarity, modifying the plist does not change the SDK that the app was compiled against. You should still expect random crashes on anything below macOS 11 if you’re building with 25r3.
You could however make a special build for those users as long as your code doesn’t do anything that’s unsupported. A branch in your VCS is a great way to handle those older versions.
3 Likes
It works perfectly on MacOS 10.15