codesign

Like many Xcode defects, this has been around for a while. If you are reading this now, consider yourself lucky you have not hit this before. See Stack Overflow for more bread crumbs, unfortunately no root cause hence no reliable workaround yet. https://stackoverflow.com/questions/52421999/xcode-10-command-codesign-failed-with-a-nonzero-exit-code

In the meantime, I found out that the problem is caused by codesign. but still no idea, why ..

I am signing the the token installer codesign --entitlements entitlements.plist --timestamp --options=runtime --sign $DEVELOPER_ID --force ./scripts/token_installer codesign --entitlements entitlements.plist --timestamp --options=runtime --sign $DEVELOPER_ID --force ./scripts/postinstall and notarising the app pkg file xcrun notarytool submit ./out/MyApp.pkg --apple-id account@account.com --team-id XXXXX --password XXXX --wait and stapling the pkg. xcrun stapler staple out/MyApp.pkg I tried moving the token_installer to Helpers but it did not help (same error). Embedding the worker in its own .app worked using another provisioning profile. But I just need to run the token installer once so it seem like an overkill to create a specific app for just one install script. This happens when the postinstall script runs on a user machine. Everything works if I make the user download the companies provision profile onto their system. Translated Report (Full Report Below) Incident Identifier: 76F6E5D1

Hello Tyronet and thank you for compiling a definitive, clear guide, foolproof even for a noob like me. I had arrived at a similar process after consulting every single thread online about the topic, collecting all the links, all the texts, and feeding everything to ChatGPT. Despite this, ChatGPT, which is unfortunately lazy and stupid, responded with the following when I asked it to compare the two guides: Comparison and Conclusions Accuracy and Details: The guide by tyronet is more detailed regarding the configuration of Startup Security Utility and the management of kernel extensions, which is a critical step for allowing unsigned extensions. My guide lacks specific details about the configuration of Permissive Security. Flexibility and Methodology: The tyronet guide focuses exclusively on a specific workflow (installation via package and then fixing permissions), while my guide offers alternatives such as using extraction tools like Suspicious Package. Reboot and Authorization Details: The tyronet guide m

In future, I’d help you if you a code block for listings like this. That makes them much easier to read. See Quinn’s Top Ten DevForums Tips for info on how to set that up. Anyway, here’s your results reformatted: % codesign -d --entitlements - -vvv /Applications/AudioMap.app Executable=/Applications/AudioMap.app/Contents/MacOS/AudioMap Identifier=com.AudioMap.AudioMap Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=383713 flags=0x10000(runtime) hashes=11980+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=56d4f956b957404261625ddf1a11633475eb70e4 CandidateCDHashFull sha256=56d4f956b957404261625ddf1a11633475eb70e4ee3454082640f96438da77c9 Hash choices=sha256 CMSDigest=56d4f956b957404261625ddf1a11633475eb70e4ee3454082640f96438da77c9 CMSDigestType=2 CDHash=56d4f956b957404261625ddf1a11633475eb70e4 Signature size=9048 Authority=Developer ID Application: Steven Gadeley (83MK4AAT9M) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=31 Jul

sgadeley@Falcon AudioMap % codesign -d --entitlements - -vvv /Applications/AudioMap.app Executable=/Applications/AudioMap.app/Contents/MacOS/AudioMap Identifier=com.AudioMap.AudioMap Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=383713 flags=0x10000(runtime) hashes=11980+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=56d4f956b957404261625ddf1a11633475eb70e4 CandidateCDHashFull sha256=56d4f956b957404261625ddf1a11633475eb70e4ee3454082640f96438da77c9 Hash choices=sha256 CMSDigest=56d4f956b957404261625ddf1a11633475eb70e4ee3454082640f96438da77c9 CMSDigestType=2 CDHash=56d4f956b957404261625ddf1a11633475eb70e4 Signature size=9048 Authority=Developer ID Application: Steven Gadeley (83MK4AAT9M) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=31 Jul 2024 at 5:41:00 PM Info.plist entries=12 TeamIdentifier=83MK4AAT9M Runtime Version=14.5.0 Sealed Resources version=2 rules=13 files=3 Internal requirements count=1 size=184 [Dict] [Key] c

[quote='760986021, scradeley, /thread/760986, /profile/scradeley'] one is more for Sandboxed app and the other is for hardened runtime. Is that correct? [/quote] We have two documentation pages that list the entitlements for each of these technologies: Hardened Runtime App Sandbox All of these entitlements an unrestricted, so they don’t need to be authorised by a profile. You just have to sign your app to claim them. My advice is that you first check what the app is claiming, then work backwards to see where things are going wrong. To do that, run: % codesign -d --entitlements - -vvv /path/to/your/built.app What do you see? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com