I’ve written a simple script that is designed to run immediately after “Install macOS Big Sur.app” has been installed. This will not actually run an OS upgrade and macOS will start to scan “Install macOS Big Sur.app” silently in the background. This would obviously lead to a bad user experience for the end user.Īs a workaround, you can trigger the code signing validation by using startosinstall -usage. There’s no way to force macOS to scan a particular app for its code signature validation other than actually trying to run it. If you run the app through the CLI using startosinstall, it will show no activity until the scan completes. If you launch the app installer through the GUI, the app will simply bounce in the dock until the scan completes. The macOS installer app for Big Sur suffers from this too and as a result if you try to run “Install macOS Big Sur.app” it will take at least 2 minutes while macOS scans it. Some apps include: Xcode, Matlab, Mathematica, etc. This results in some really large apps taking 2-3 minutes before they can run. As part of Gatekeeper, macOS runs a code signature validation scan on all apps when they are run the first time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |