However, this choice affects how you package your product, something discussed in more detail below.Īll code that you distribute must be signed. For example, you might have an app inside an installer package on a disk image.Įach container format has its own pros and cons, so pick an approach based on the requirements of your product. In contrast, products distributed outside of the Mac App Store can use a variety of different container formats, the most common being: Mac products support two distribution channels:Īn app can be distributed via the Mac App StoreĪpps and non-apps can be distributed outside of the Mac App Store using Developer ID signingĪ Mac App Store app must be submitted as an installer package. To get started, decide on your container format. If you’re using a third-party development environment, consult its support resources for advice before continuing. Many third-party development environments have their own strategies for signing and packaging the products they build. Note If you find this post a little abstract, and would prefer to follow a concrete example, see Manual Code Signing Example.Ĭonsult Resources for Third-Party Development Environments In these cases you must manually sign and package your product. For example:Īn app that’s distributed outside of the Mac App Store on a disk imageĪ product that has to be installed via an installer packageĪn app that uses a third-party development environment However, not all Mac products can be distributed this way. See Xcode Help > Distribute your app for the details. The best way to sign and package an app is via Xcode: Build a version of your app to distribute using Xcode’s Product > Archive command, and then package that archive for your distribution channel via the Organizer. IMPORTANT None of the following has been formally reviewed, so it’s not official Apple documentation. Or, if you want one-on-one help, open a DTS tech support incident and we can pick things up in that context. I’ve locked this thread, so just start a new thread tagging it with Code Signing, Notarization, or Gatekeeper. And if have any questions about this, it’s probably best to ask them here on DevForums. If you have any corrections, feel free to get in touch with me directly (my email address is in my signature). And rather than keep that to myself, I’m posting it here for everyone’s benefit. The instructions for how to sign and package a Mac product for distribution are rather scattered, so I’ve written them all down in one place. I spend a lot of time helping Mac developers with notarisation and Gatekeeper problems, and many of these problems are caused by incorrect code signing. I’ve left the original post here just for the record.Īpple Developer Relations, Developer Technical Support, Core OS/Hardware See the preamble in Creating Distribution-Signed Code for Mac for more context. Joe brings that same passion to How-To Geek.IMPORTANT This post has been replaced by two shiny new posts:Ĭreating Distribution-Signed Code for Mac If something piques his interest, he will dive into it headfirst and try to learn as much as possible. Outside of technology, Joe is an avid DIYer, runner, and food enthusiast. After several years of jailbreaking and heavily modifying an iPod Touch, he moved on to his first smartphone, the HTC DROID Eris. He got his start in the industry covering Windows Phone on a small blog, and later moved to Phandroid where he covered Android news, reviewed devices, wrote tutorials, created YouTube videos, and hosted a podcast.įrom smartphones to Bluetooth earbuds to Z-Wave switches, Joe is interested in all kinds of technology. He has written thousands of articles, hundreds of tutorials, and dozens of reviews.īefore joining How-To Geek, Joe worked at XDA-Developers as Managing Editor and covered news from the Google ecosystem. Joe loves all things technology and is also an avid DIYer at heart. He has been covering Android and the rest of the Google ecosystem for years, reviewing devices, hosting podcasts, filming videos, and writing tutorials. Joe Fedewa has been writing about technology for over a decade.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |