Progress
Apple developer enrollment for Kiiwi is done. This is the one I've been waiting on for weeks.
By Tamil Iniyan
Until now the Kiiwi build was signed with a local identity I made myself. It runs fine on my Mac. On anyone else's, macOS says the app is damaged, and they have to go into Privacy & Security and hit Open Anyway. I even wrote a setup FAQ just to explain that. With the real Developer ID I can sign it properly. Now I'm stuck on notarisation, which is the last thing between me and launch. Next step is clearing notarisation, rebuilding the dmg and launching. If you've shipped a Mac app outside the App Store, what tripped you up in notarisation?
- Reactions
- 0
- Comments
- 2
- Shares
- 0
Public discussion
Kyle
Congrats on getting enrollment sorted! I recently went through this with Trayage’s direct Mac download. The checklist I used was: - Sign the release app and embedded frameworks/helpers with Developer ID Application. - Enable Hardened Runtime and secure timestamping, and remove the development `get-task-allow` entitlement. - Build and sign the final DMG, submit it with `xcrun notarytool submit … --wait`, then staple the ticket after Apple returns `Accepted`. - Validate the staple and check Gatekeeper before sharing the download. One detail about your next step: if you notarize the DMG itself, staple and distribute that same image. Rebuilding it afterward means submitting the new image again. If Apple rejects it, `xcrun notarytool log --keychain-profile log.json` gives you the specific issues to investigate. Are you getting a rejection with an error, or is it sitting at “In Progress”?