"No iOS signing identities match the specified provisioning profile" when there are multiple profiles with the same name

[chamons]

If you have multiple profiles with the same name linked to different certificates the iOS signing set can get very confused.

Originally in internal bug but this appears to be unrelated to IDE integration

I've been able to reproduce it by using Manual Provisioning and selecting a specific certificate and provisioning profile, but Automatic Provisioning makes it easier to reproduce because it always creates certificates with the same name (VS:WildCard Development).

Workaround

Select Manual Provisioning and then select Automatic as Signing Identity and Provisioning Profile.

Steps to Reproduce

1. Setup multiple different profiles with the same name linked to different certificates. This can be done easier as Automatic signing will create "VS:WildCard Development".
2. Try to build (locally on mac or over remote Windows connection).
3. error : No iOS signing identities match the specified provisioning profile 'VS: WildCard Development'.

Expected Behavior

Either a specific error stating situation or successful build.

Actual Behavior

Confusing build error

Environment

Build Logs

Build Output - DetectSigningIdentity failed.txt

Example Project (If Possible)

None. Any new iOS project will repro if certificates in correct "bad" state.

[sherif-elmetainy]

I have the same issue when I use Automatic provisioning.
It seems that automatic provisioning would create a signing certificate %USERPROFILE%\AppData\Local\Xamarin\iOS\Provisioning\Certificates but since the actual signing occurs on the macOS computer, the macOS doesn't have the private key for the signing certificate.

At the moment I am trying to look into ways to export that .p12 certificate file. There is a corresponding .pass file having the same name. But I can't figure out the format in which the password is stored.

[dantoine]

Usering KeyChain Access on remote host Mac may help to export a .P12 certificate (Login > My Certificates > Right-click on the certificate > Export), which you then have to import in local Visual Studio (Tools > Options > Xamarin > Apple Accounts > Show Details).

However, despite being able to type the password for the certificate in VS, it is not loaded in the certificate list. It appears it is not loaded in background either, as I have the same issue as OP. ("No iOS signing identities match the specified provisioning profile" - may be unrelated to this issue)

Looks like a bug to me