-
Notifications
You must be signed in to change notification settings - Fork 9
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
createInstallMedia for x86-only OSes won't run on M1 #2
Comments
I dug into the crash logs and found this interesting line: Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) So it looks like it's the older versions dying not because of any architecture or in-coded issues, but due to the expired certs. Can probably be fixed via a date change on the host. Maybe a cert expiry check at the beginning with an error line emitted if this is the case? Or even better... I know there's a way to set the reported date ONLY for a specific process tree. I can't recall how it's done though. The alternative would be to set the time before running createInstallMedia and then set it back immediately after starting the process, so as to minimize impact elsewhere on the system. |
Issue just seems to be on High Sierra through Catalina. Changing the date doesn't appear to fix it, neither does stripping extended attributes. |
I found a solution: from the Terminal, run: |
I got |
Solved in v1.1.0 |
Just thought I should give you a heads-up: if I attempt to run a pre-M1 createInstallMedia on my M1 Mac running Monterey, I'm greeted with the response of: "Killed: 9".
This breaks pretty much every conversion script out there that depends on createInstallMedia, including yours. So a new requirement of createInstallMedia appears to be that you're running an x86 version of macOS.
I wonder if https://gist.github.com/julianxhokaxhiu/6ed6853f3223d0dd5fdffc4799b3a877 could be updated to work for any OS from Mountain Lion through Big Sur without a dependency on createInstallMedia?
Lion, of course, works just by copying the InstallESD.dmg.
The text was updated successfully, but these errors were encountered: