So assuming you’ve exported your iOS app archive to ~/spfexpert/iamgroot/build, you could copy the ist as follows: I’ve already documented how to snag this file so review that post for more details. This is a required configuration that you could create manually but is saved by Xcode when you archive an app. The generated password for temp/temp there are temporary passwords for me, I just overwrite it. Add generated password for temp/temp.ġ file changed, 0 insertions(+), 0 deletions(-) You can use whatever technique you like but I’ve been a huge fan of of zx2c4’s password-store for many years now and generate the password as follows: pass generate temp/temp 18Īn entry already exists for temp/temp. The last step is just to create a password you will use to setup and add data to the GitHub Action macOS runner’s Keychain. $ cp ~/Library/MobileDevice/Provisioning \ Profiles/1d0e8da1-9eba-41c7-a308-931ba380c3b0.mobileprovision ~/spfexpert/ios-deploy/Ģ.3 Keychain password for the build machine The provisioning profiles are stored on your macOS at ~/Library/MobileDevice/Provisioning\ Profiles so you can simple copy the appropriate files as follows: Using the little hack of looking at the CodeSign output from a command line build, we can see which provisioning profile Xcode used. The next item we need is the mobile provisioning profile. Once I saw this, it was obvious that I needed the first certificate in Keychain Access! 2.2 Mobile provisioning profile for the app Provisioning Profile: "iOS Team Provisioning Profile: *" Signing Identity: "Apple Development: Andrew Hoog (ZJN98QQ2HM)" As you can tell above, I have two certificates and while working on the Github Action, I chose the wrong certificate multiple times! One way to figure out the appropriate certificate to build the app from the command line on your macOS and look for the CodeSign output in logs, e.g.: CodeSign /Users/hiro/Library/Developer/Xcode/DerivedData/I_am_Groot-gfxpkzbpazztxzabhewsezcfrozd/Build/Products/Debug-iphoneos/I\ am\ Groot.app (in target 'I am Groot' from project 'I am Groot') If you’re just starting out with iOS development, it’s likely you might have just a single certificate. Tip: finding the correct signing certificate and provisioning profile Enter strong password to protect the certificate. ![]() Choose your location ( ~/spfexpert/ios-deploy) and file name (defaults to Certificates.p12).Right-click your certificate and select “Export…”.Select “My Certificates” from horizontal navigation.Select login on left “Default Keychains” panel.Since you’ve already built your app in Xcode, you can simple run Keychain Access (just do a Spotlight Search by hitting ⌘-Space) and do the following: $ mkdir -p ~/spfexpert/ios-deploy & cd $_ 2.1 Signing certificate To simplify access to these inputs, please all the files in a single folders, e.g.: But I’m lazy and realized that Xcode already did all of this for me so I could simple reuse what was already configured (ymmv)! There are plenty of blogs that step you through the process of creating the first three items manually in Apple’s Developer Portal so feel free to check them out. Keychain password for the build machine.Mobile provisioning profile for the app. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |