从MacBook Pro迁移至MacBook Air后，Xcode上传TestFlight提示Apple Distribution证书私钥缺失的解决方法咨询

Hey there, I get it—migrating to a new Mac and hitting code signing issues is super frustrating, especially when you don't want to recreate existing certificates. Let's walk through the exact steps to find and transfer the correct private key from your old MacBook Pro to your new Air:

Step 1: Precisely Locate the Correct Private Key on Your Old MacBook Pro #

Since you know the certificate's ID (ZH24....) and expiration date (2021-09-02), we can directly tie it to its private key:

• Open Keychain Access on your old Mac.
• Switch to the Certificates tab (top left).
• Scroll through the list to find the Apple Distribution certificate that matches your expiration date (2021-09-02). To confirm it's the right one, right-click the certificate, select Get Info, and check the Organizational Unit field—it should show your target random ID (ZH24....).
• Once you've confirmed the certificate, click the small arrow next to it to expand the entry. The private key associated with this certificate will be listed directly below it (it'll have the same name as the certificate).

Step 2: Export the Certificate + Private Key Pair #

It's critical to export both together to avoid pairing issues later:

• Hold down the Command key and select both the certificate and its corresponding private key.
• Right-click the selected items and choose Export 2 items....
• Save the file in the Personal Information Exchange (.p12) format.
• Set a secure password for the file (you'll need this when importing on your new Mac), then save it and send it to your new MacBook Air via AirDrop, USB, or cloud storage.

Step 3: Import the .p12 File on Your New MacBook Air #

• Double-click the .p12 file you transferred. Keychain Access will open automatically.
• Enter the password you set during export, and make sure the file is imported to the login keychain (this is the default setting, and it's the right choice for Xcode access).
• Once imported, open Xcode and go to Settings > Accounts. Select your Apple ID, then click Manage Certificates. Refresh the list—you should now see your Apple Distribution certificate with its private key properly paired (no more missing key errors!).

Bonus: Alternative Method via Xcode Account Export #

If you have the same Apple ID logged in on both Macs, this can be even easier:

• On your old Mac, open Xcode > Settings > Accounts. Select your team's account.
• Click the small gear icon in the bottom-left corner of the Accounts window, then choose Export Accounts....
• Save the exported file (it'll include all your certificates, keys, and account settings) and transfer it to your new Mac.
• On your new Mac, open Xcode > Settings > Accounts, click the gear icon again, and select Import Accounts.... Select the exported file, enter the password if prompted, and Xcode will automatically sync all your signing assets.

Quick Troubleshooting Tip #

If you still see errors after importing, check the private key's trust settings in Keychain Access:

• Find the imported private key, right-click > Get Info.
• Go to the Trust section, set Code Signing to Use System Defaults (this is usually sufficient, but if issues persist, you can temporarily set it to Always Trust and test again).

That should get your new MacBook Air ready to upload to TestFlight without having to recreate any certificates.

内容的提问来源于stack exchange，提问作者Burak