Skip to content

Conversation

iCMDdev
Copy link

@iCMDdev iCMDdev commented Oct 4, 2025

This PR updates an availability check for a SwiftUI .titleAndIcon label, which allows decreasing the minimum deployment to macOS 11.0.

This allows UTM 4.x to build & run on earlier versions of macOS Big Sur (11.x < 11.3).

@iCMDdev
Copy link
Author

iCMDdev commented Oct 4, 2025

Note that I haven't changed the minimum deployment-related Xcode files in this PR, yet.

@iCMDdev
Copy link
Author

iCMDdev commented Oct 4, 2025

Now it should be done.

@osy
Copy link
Contributor

osy commented Oct 4, 2025

Have you tried building and testing it?

@iCMDdev
Copy link
Author

iCMDdev commented Oct 5, 2025

I followed the instructions here (downloaded sysroot-macOS-arm64 from GitHub Actions) and succesfully built from Xcode 26 (on macOS 26). I didn't get any build errors, but I haven't tested the resulted app on macOS 11.x < 11.3.

Earlier (before making this change), I had access to a Mac on 11.2.3, and I manually changed the minimum version of the official (latest) binary using vtool, which resulted in an Undefined symbol crash (in SwiftUI if I recall correctly). I think that was likely caused by the .titleAndIcon label style, which is unavailable on macOS versions < 11.3.

Xcode indeed throws this error if I change the minimum deployment on the currrent main branch (unmodified) code:

Xcode error

@iCMDdev
Copy link
Author

iCMDdev commented Oct 5, 2025

Visually, I haven't seen anything else that requires macOS 11.3 or later, other than this, but I could be wrong - though building seems fine.

@osy
Copy link
Contributor

osy commented Oct 5, 2025

If I remember correctly, there was a number of SwiftUI bugs that was fixed in 11.3. I don't recall the full list off the bat, but I would try testing VM creation, config (all the tabs, changing all the options), app preferences, and moving around VMs on the home screen.

@iCMDdev
Copy link
Author

iCMDdev commented Oct 5, 2025

I'll test and see. Either way, if you consider it's better to keep 11.3 as a minimum target, I think it's fine (and people can / should upgrade either way).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants