dotnet / dotnet/macios

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

Open
#13,016 2 comments 0 reactions 0 assignees View on GitHub
bug iOS
Dominant language
C#
Stars
2.9k
Forks
576
Avg merge
2d 12h
Merged PRs (30d)
123

Description

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](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1418343) 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](https://github.com/xamarin/xamarin-macios/files/7365642/Build.Output.-.DetectSigningIdentity.failed.txt)

### Example Project (If Possible)

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.