Quiz · 4 questions

🔏 Bundles, Signing and Grants

From a build product to a signed app, the requirement that names it, a self-signed identity on purpose, TCC, Keychain ACLs, and the roads not taken

Level 0Bundle Opener

0 XP0/81 lessons0/17 achievements

0/100 XP to next level100 XP to go0% complete

Quiz

01An ad-hoc signed Mac app asks for Accessibility again after every rebuild, even though its bundle identifier never changes. Why?

02A build script checks for the family's self-signed identity with security find-identity -v -p codesigning, finds nothing, and falls back to ad-hoc. The identity is in the login keychain. What went wrong?

03An app moved from ad-hoc signing to a stable self-signed identity, and its designated requirement is verified stable. One Keychain read still prompts every time. What is the deterministic fix?

04A self-signed app bundles a dylib signed with the same certificate. After adding --options runtime, the app fails to load it with "different Team IDs". Why?

← PreviousThe Roads Not Taken: Hardened Runtime, Notarization, Sandbox 🏛️ Living as a macOS Citizen →LaunchServices and the One Slot in /Applications

Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)

No comments yet — be the first.