macOS Sequoia is not getting upgraded when we try using Jamf policy with erase-install launcher script

[pveenu]

Describe the bug macOS Sequoia is not getting upgraded when we try using erase-install launcher script with Jamf.

To Reproduce

• If applicable, please provide the full command used when running the script -- we have used the erase-install package version : 35.0 and used the following command with erase-install launcher script: --reinstall --beta --catalog 15
• Please describe how the script was run -- in Jamf Policy from the uploaded pkg Expected behavior Device was supposed to upgrade to macOS Sequoia but here when we check the logs its downloading the macOS Sonoma 14.5.

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:

your log goes here between triple backticks! Make sure you remove any personal information!

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS version - 14.4.1
• erase-install version [35.0] Additional context Add any other context about the problem here.

[grahampugh]

Please post the log.

[pveenu]

erase-install.log

Attached is the log file. I also used the --depnotify parameter for notifications, but it was defaulting to using SwiftDialog. Please see the attached image for reference.

[grahampugh]

Something on your computer is preventing the disk image from unmounting, which causes Mist to fail, as shown in the logs:

Invalid Exit Status Code: '16', Message: hdiutil: couldn't eject "disk4" - Resource busy

Often this is due to some sort of security or scanning software that is preventing the disk image from either mounting or unmounting.

--depnotify mode does not exist since erase-install version 28.0. If you want to use DEPNotify you'll have to go back to version 27.3.

[pveenu]

We encountered that error code because the upgrade was canceled due to it attempting to install macOS Sonoma instead of macOS Sequoia. The logs indicate that it only searches for macOS Sonoma installers, even though we used --beta and --catalog 15 to obtain the macOS Sequoia installers. Attached the image for reference.

Note: There are no restrictions applied to this device. When we execute the terminal commands manually on the same device, they work as expected. However, we see this issue only when we attempt it using the Jamf policy.