You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I noticed the "Upgrading macOS" dialog was using the "warning" icon instead of a macOS icon when I ran a simple --test-run --reinstall command. Confirmed icons were in icons directory, permissions were correct, etc., but erase-install.sh kept showing the "warning" icon instead, and only on one of my test Macs, not others.
Narrowed it down to the fact that the /Applications directory on this one test Mac had two copies of the installer, one named Install macOS Sonoma.app and one named Install macOS Sonoma Copy.app and erase-install.sh picked up the Copy instead of the regular name, and was using that in various parts of the script, including for determining the dialog icon.
Since it can't find or download /Library/Management/erase-install/icons/Install macOS Sonoma copy.png it reverts to the warning icon.
To Reproduce
Create a copy of Install macOS Sonoma.app in /Applications
If applicable, please provide the full command used when running the script. ./erase-install.sh --test-run --reinstall
Please describe how the script was run. Terminal
Expected behavior
The "Upgrade macOS" dialog to show the macOS Sonoma icon.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS version 14.6.1
erase-install version 37.0
Additional context
This is just an example of unexpected behavior. Having a non-standard installer name for a valid installer may cause other issues, but I haven't tried to track those down. A potential solution could be to more strictly match to standard macOS installer names, but not sure if this particular situation is too much of an edge-case for real concern.
(Having multiple installers with standard install names in the same location, like both/Applications/Install macOS Sonoma.appand/Applications/Install macOS Sequoia.app may also cause unexpected behavior, though specifying --os or --version or --build would I assue mitigate most of those issues.)
The text was updated successfully, but these errors were encountered:
Describe the bug
I noticed the "Upgrading macOS" dialog was using the "warning" icon instead of a macOS icon when I ran a simple
--test-run --reinstall
command. Confirmed icons were inicons
directory, permissions were correct, etc., buterase-install.sh
kept showing the "warning" icon instead, and only on one of my test Macs, not others.Narrowed it down to the fact that the
/Applications
directory on this one test Mac had two copies of the installer, one named Install macOS Sonoma.app and one named Install macOS Sonoma Copy.app anderase-install.sh
picked up the Copy instead of the regular name, and was using that in various parts of the script, including for determining the dialog icon.Since it can't find or download
/Library/Management/erase-install/icons/Install macOS Sonoma copy.png
it reverts to the warning icon.To Reproduce
Create a copy of Install macOS Sonoma.app in
/Applications
Expected behavior
The "Upgrade macOS" dialog to show the macOS Sonoma icon.
Code/log output
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
This is just an example of unexpected behavior. Having a non-standard installer name for a valid installer may cause other issues, but I haven't tried to track those down. A potential solution could be to more strictly match to standard macOS installer names, but not sure if this particular situation is too much of an edge-case for real concern.
(Having multiple installers with standard install names in the same location, like both
/Applications/Install macOS Sonoma.app
and/Applications/Install macOS Sequoia.app
may also cause unexpected behavior, though specifying--os
or--version
or--build
would I assue mitigate most of those issues.)The text was updated successfully, but these errors were encountered: