-
Notifications
You must be signed in to change notification settings - Fork 303
Script fails with macOS 12.3 on Apple Silicon due to "bless" option not supported #127
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
Comments
Please attach the output of It works on 12.2.1 so maybe they removed that option it the 12.3 beta. |
12.3 was released today. |
That doesn't help much as all options are listed. However |
I'm updating to 12.3 to test that one. Just checked that not using that option does not seem to affect on the DMG opening in the Finder when mounted. Will test tomorrow on older OSs and if not using that argument does not affect on most OSs maybe we can get rid of it instead of detecting Silicon and limiting to Intel or 12.2.1-. |
I tested with the whole line removed and also with the offending part removed:
In both cases it seemed to be OK. |
Indeed! Tested it in as low as Mac OS X 10.6. So maybe that bless was only needed in older OSs. Probably then the best way is to set the bless step as optional and not used by default. |
I have the same problem after upgrading to macOS 12.3 on Mac Mini M1 with original stable version of create-dmg script. |
Suggested change to remove "bless --folder ... " line cures the problem. |
Seems to have no effect on modern OSs and is no more compatible on macOS 12.3 with Silicon #127
Just released 1.0.10 with this issue fixed: https://github.com/create-dmg/create-dmg/releases/tag/v1.0.10 |
Thanks for the fast response. 👍 |
Since macOS 12.3 on Apple Silicon the "bless" part of the script gives the following error and the script fails:
bless: The 'openfolder' is not supported on Apple Silicon devices.
Commenting out this line succeeds:
bless --folder "${MOUNT_DIR}" --openfolder "${MOUNT_DIR}"
The text was updated successfully, but these errors were encountered: