It looks like that DeviceSupport directory only has X.Y versions, not X.Y.Z. The next time running the app from Xcode still took a little extra time it said something about copying cache files to my phone I assume that's related to the 14.5 stuff I just added with the above instructions.Īlso, ferFrassia mentioned 14.5.1 vs. (Yes, I quit Xcode before copying, then started Xcode again.) After doing the same thing through the Finder, it worked. I don't remember if it was a different error message than the unsupported iOS version, but it didn't work. I used the command line the first time ( sudo cp -r …), and Xcode didn't like it. Robske_110 missed "Platforms" in the directory path: It's Xcode.app/Contents/Developer/Platforms/atform/DeviceSupport/14.5īe sure to use the Finder to copy the directory. If you have questions or issues with notarization, Apple's references is a good starting point for investigation.Robske_110's response was very helpful, but two notes: The post on How to Check if a macOS App is Notarized describes the verification steps. It can be useful when you have an app or installer package and you want to know if it is notarized. Verifying notarization is not a mandatory step after exporting a notarized app. You now have an app that can be distributed outside the Mac App Store. Choose Window > Organizer.Ĭlick on Export Notarized App to save the app to your chosen location. If the Organizer is closed, open it from the Xcode menu. For this post, notarization only took about 30 mins.įrom the Organizer, choose the archive, and scroll down. You will receive a notification and an email to your Apple ID once the notarization is complete. Once the upload is complete, wait for Apple's notification. You can monitor the upload progress as shown. If the Summary and Entitlements are as expected, click Upload to upload the app to Apple's notarization service. Choose Upload in the destination window.Ĭhoose Automatically manage signing in the signing options window. Though there is an option to export without notarizing, always choose to notarize as notarization enables automated scans of your app. If there are no issues, the notary service generates a ticket for you to staple to your software the notary service also publishes that ticket online where Gatekeeper can find it.įrom the Organizer, click on the Distribute App button to start the distribution process. The Apple notary service is an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly. Notarization gives users more confidence that the Developer ID-signed software you distribute has been checked by Apple for malicious components. You are now ready for the next step: notarization. The Organizer window launches showing the archive. When you are ready to distribute your app, the first step is to archive the application.įrom the Xcode menu, choose Product > Archive. Set your Xcode project's Deployment Target to at least 10.9 Notarization only works for binaries linked against macOS 10.9 or later. You can check if you have a Developer ID certificate in your keychain by running the following command from the Terminal.Įnter fullscreen mode Exit fullscreen mode p12 extension) can be installed on any Mac machine. Once the certificate is generated and the private key exported from the Account Holder's keychain, the exported key (with a. Only an Account Holder can generate a Developer ID certificate. The Developer ID private key must be installed on your Mac keychain.Īpple describes a Developer ID certificate as.Ī Developer ID certificate lets Gatekeeper verify that you’re a trusted developer when a user opens your app, plug-in, or installer package downloaded from outside the Mac App Store. This post describes how to check if your Apple ID is setup correctly. Your Apple ID must be registered to the same Developer account where the Developer ID came from. To enable automatic signing, Xcode needs to connect to the Developer portal with an Apple ID registered to a Developer account. Distributing installers is not covered however the steps are fundamentally the same.īefore beginning the app export process, ensure the following are installed and present.Īlthough Xcode 10 will work, Xcode adds the secure timestamp from Xcode 10.2. At this point it is assumed that the decision has been made to distribute outside the App Store. The different distribution methods are described by Apple. This post covers publishing of macOS applications outside the Mac App Store.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |