-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors when upgrading to macOS Sequoia if invalid macOS installers are present using --update option #529
Comments
Checking the jamf logs we see the following error: 2024-10-30 08:30:48 | v36.0 | [erase-install] ERROR: Invalid installer is present. Run with --overwrite, --update or --replace-invalid option to ensure that a valid installer is obtained. We are using an erase-install-launcher script with along with the package in Jamf and we used one of the parameter as --reinstall --overwrite |
Hi, you need to fill in the bug report properly or I can't help you. The one line you've provided shows me that you've used an invalid combination of parameters. |
Hi, |
Hi, thanks for the logs. You have found an edge case bug which I will fix in the next release, coming soon. You may be able to solve it now by using the |
Thank you for addressing the issue so promptly! |
Describe the bug
We are experiencing errors when upgrading to macOS Sequoia if previous macOS installers, like Install macOS Ventura.app, are located in the /Applications folder.
To Reproduce
Expected behavior
Device was supposed to be upgraded to Sequoia even if other macOS installers present in /Applications folder.
Code/log output
Please supply the full command used, and if applicable, add full output from Terminal or from
/var/log/erase-install.log
. Don't post a partial log - I need the whole thing. Either upload the log as a file, or paste the output in a code block like this:Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: