How do I set the minimum macOS version?
Setting the value in the IDE (2024r1) doesn’t do anything at all. I still get 10.14 and not 11.0.
Then I tried with an info.plist and get this gem:
How do I set the minimum macOS version?
Setting the value in the IDE (2024r1) doesn’t do anything at all. I still get 10.14 and not 11.0.
Then I tried with an info.plist and get this gem:
The minimum macOS version is an item on the macOS build tab (at least in later versions). It’s quite likely that your plist entry is being added to by Xojo. 10.14.0 is the default value.
Actually I think you are saying that putting 11 in Xojo doesn’t remove the 10.14. Could be a bug. Just testing
It seems fine for me. If I set it in the IDE the comes out correct in the built application:
Do you have your own plist in the Xojo or adding items externally, using defaults or plistbuddy
That’s what I said above.
Then I tried with an info.plist and get this gem:
And the I tried this:
PropertyValue("App.MacOSMinimumVersion") = "11.0"
I think attempting to set it in a script and having it within the IDE are clashing. I think you’re stuck with only doing it manually on the macOS settings. It’s likely a bug that updating it via script isn’t working.
Using the IDE macOS setting and nothing else (like scripts or plist entries) works correctly for me.
I really don’t see that being possible. The settings you set in a script are coalesced and rendered just as the package is generated.
Same here, even downloaded 2024r1 to test.
That doesn’t seem to be true for this new setting. It looks like Xojo is adding the item twice. Certainly seems to be the case in the example provided.
If so, that’s a bug. The IDE certainly is capable of handling this.
I tried some tests and I was not able to make it fail:
I hope you can find the problem.
I’m now using an IDE script because nothing else works. If this was an IDE bug it should have been noticed.
To be fair to Xojo, just adding the property can make it scriptable and you don’t always think about all of the places a thing like this will be exposed. With a Q/A team of one, things like this are going to slip by.
I’ll do some testing with the latest version. It should have worked either for the IDE property or the app property set with a script or the plist. So for me this looks like some corruption in my old project.