grahampugh / erase-install

A script that automates downloading macOS installers, and optionally erasing or upgrading macOS in a single process. Watch the video!
https://grahamrpugh.com/2023/05/14/macaduk-presentation-eraseinstall.html
Apache License 2.0
845 stars 132 forks source link

[FR] Restrict SwiftDialog version to 2.2 on macOS 11 #392

Closed grahampugh closed 1 year ago

grahampugh commented 1 year ago

Is your feature request related to a problem? Please describe. SwiftDialog 2.3+ will only work on macOS 12 and above. In order to provide N-3 support, which is essential for erase-install moving forward, we need to ensure that we use swiftDialog 2.2. Currently erase-install will download 2.1 (soon 2.2) if it is not present, but if a newer one was present it would not attempt to downgrade it.

Describe the solution you'd like We should continue to specify version 2.2 for downloads and in the package, and if macOS is version 11 we should also ensure that version 2.2 gets installed even if 2.3+ is there.

Additional context Note that there should not be a big problem here since it only affects macOS 11 and there should be few circumstances where SwiftDialog 2.3 would have ended up on macOS 11.

grahampugh commented 1 year ago

This should be addressed with v30.0.

Samstar777 commented 1 year ago

@grahampugh I just tested your v31 on Apple Silicon device and its installing SwiftDialog v2.3.2 on macOS Big Sur. Let me know if I can help you with any logs

grahampugh commented 1 year ago

How did you install? The package does contain 2.3.2 but when you run the script on macOS 11 it should delete it and download the older version.

Samstar777 commented 1 year ago

I am using Erase-Install-31.0.Pkg through Jamf Pro with command in files and process </Library/Management/erase-install/erase-install.sh --os Sonoma --reinstall --current-user --confirm>

grahampugh commented 1 year ago

And did it remove 2.3.2 and download 2.2.1? Can you ship me the logs if not?

Samstar777 commented 1 year ago

It is not downgrading to v2.2.1, in fact i had installed v2.2.1 and the script upgraded the same to v2.3.2 erase-install.log

grahampugh commented 1 year ago

Thanks, I'll try and spin up a Big Sur VM when I get a chance.

allanp81 commented 1 year ago

While I haven't figured out exactly why, it seems that it might be line 252 that's the problem, possibly because it can't read the version properly?

Samstar777 commented 1 year ago

Also, Do let me know if you want to have remote access on my Big Sur mac. If you can't spin a Big Sur VM

grahampugh commented 1 year ago

This should be fixed now, please try the latest v31.0 that I pushed just now.