Can't Build Ad-hoc Locally - Profile Doesn't Include My Cert

Question

Created May ’21

Replies 1

Boosts 0

Views 2.5k

Participants 2

I am trying to debug our build machine by running the scripts locally. But I can't do Ad Hoc builds on my local dev machine.

The error message is

*** Ad Hoc Distribution" doesn't include signing certificate "Apple Development: Paul Wilkinson

In Xcode when I try to select the Ad Hoc Distribution profile in Signing & Capabilities I get the same error message and the profile is Ineligible.

I tried downloaded the certificate from the developer site but when I open it it does not appear in my keychain.

I could not find a way to add my certificate to the profile.

I did a lot of searching for solutions but I cannot use automatic provisioning on the build machine.

Any suggestions? Cheers!

Boost

Answer 1

Systems Engineer OP

Apple

Jun ’21

To resolve this one thing you could try is creating a new Distribution Provisioning Profile with the Certificate that you created on your Development machine. You should be able to see this Certificate in the Developer portal because this is the one that you download after you created the CSR from your Keychain. If you are not on the machine that you created the CSR from, then find that machine and run through the process on that machine. The process would include:

Find the expiration of your Development Certificate that was created from your CSR.
Go to the Developer Portal and create a new Ah-Hoc Provisioning Profile for your App, and match the Developer Certificate that you identified on your machine.
Include all devices for this Provisioning Profile that are needed.
Download the Provisioning Profile onto the machine and then verify that the Certificate attached is the same one you have attached to your signing identity in the Keychain. For example, you should be able to go to the Keychain and see the Certificate attached to your profile. You should also be able to click the arrow to the left of your Certificate and see the private key attached to the Certificate because your CSR was created on this machine. This makes up your signing identity for signing an App.
You should a this point be able to test this profile with at least manual code signing or as assigned in your build scripts. When exporting, if you need to you should be able to also identity this profile to be used during the export.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

0