Quick Links

I get the above error when trying to build my app and publish to TestFlight.

I have gone in circles trying to clear out and recreate certificates and provisioning profiles, with no luck.

I was able to create this successfully when using a first certificate, but as TestFlight errored out because I had no devices attached to that provisioning profile, I had to recreate the certificate. Since doing this I have encountered this error.

Right, so you created a new certificate, but did you add the certificate to the Provisioning Profile on Apple's Developer Portal and then re-download/install the Provisioning Profile?

You need to do that.

The Provisioning Profile you have installed on your machine was created before you created your certificate, so there's no way it can have your certificate embedded inside of it.

If you open up ~/Library/MobileDevice/Provisioning Profiles/<guid>.mobileprovision, you'll see that it has <key>DeveloperCertificates</key> which has an array of certificates as the value. Only certificates in that list can codesign an app using that Provisioning Profile.

Once you edit it on Apple's Developer Portal to add your certificate to that Provisioning Profile, you'll need to re-download it and install the new copy and then select that in the Project Options.

Way cool - I'd never opened up a provisioning profile in a texteditor before.

I managed to track it down to various projects not using the right profile, and things possibly getting mixed up because of duplicate names etc. All sorted now - thanks for your help Jeffrey, and keep up the great work :-)

I have a similar situation. In Xcode Developer preferences I can see that I have valid Signing and provisioning profiles. When in Xamarin the Project Project options is grayed out. In Xamarin preferences I see a valid provisioning profile but not signing profile.
I'm pretty confused.

I have the same issue. I went so far as to generate a new provisioning profile that used a new certificate and it's STILL barfing when I try to build via Xamarin.

I downloaded every distribution certificate available in developer.apple.com and double-clicked it to install it in Keychain. I see the certificates there, and they all say "This certificate is valid" when I click on them.

I popped open the provisioning profile with the GUID from the error, and under the <key>DeveloperCertificates</key>
dictionary entry, it just has:<array><data>(a giant, 30 or so line string of random characters)</data></array>

What I did was I deleted the provisioning profiles (off my local machine) as well as the certificates and reinstalled them. Then, even after a reboot it did not work. But to make it work I opened Xamarin and went to Preferences > Developer Accounts > [selected my account and clicked view details] > REFRESH

After the provisioning profiles were refreshed then it had the new profiles in there and it worked again.

I am having exact problem. I am creating provisioning profile for in-house distribution. First I created AppId and then I created Distribution Certificate, finally I created provisioning profile with distribution certificate. After creating profile, I refreshed Xcode and my profile was listed in that. In Xamarin under iOS Bundle Signing tab, in-house provisioning profile is listing under developer signing code, not for distribution.

If I select Distribution (Automatic) identity, my profile is shown and if I choose my profile, its showing compile error as below:

I am able to build ipa without any error in developer signing code, but it is actually distribution profile. What could be the problem, many times I recreated certificate & profile. I am creating & opening certificate in same Mac machine only.

SOLVED: I had the same darn issue and was searching for hours for a solution. I am on free provisioning, and the dummy application I created in XCode during the free provisioning setup process (https://developer.xamarin.com/guides/ios/getting_started/installation/device_provisioning/free-provisioning/) was running on my connected iPad fine. I had checked the bundle identifier (com.xxx.yyy) in XCode and Xamarin Studio were the same in Info.plist and everything. The problem was when I tried to run my app from Xamarin Studio on the same iPad, I got an error during the build.

TO FIX: In XCode, change the text of the bundle identifier manually to something else at the end. For example, my old one was "com.Mika.calc" and I changed it to "com.Mika.calc-" just by adding a space at the end. Immediately, a message will appear in XCode below the box you typed the text in that says "no matching profiles matching the bundle identifier were found," and below that there will be a button labelled "Fix Issue." CLICK THAT.
Now, copy the new bundle identifier and paste it in the Info.plist file of your project in Xamarin Studio. Now, when you go to [yourProject].iOS > Options > iOS bundle signing everything should be fixed.

@MikaY said:
SOLVED: I had the same darn issue and was searching for hours for a solution. I am on free provisioning, and the dummy application I created in XCode during the free provisioning setup process (https://developer.xamarin.com/guides/ios/getting_started/installation/device_provisioning/free-provisioning/) was running on my connected iPad fine. I had checked the bundle identifier (com.xxx.yyy) in XCode and Xamarin Studio were the same in Info.plist and everything. The problem was when I tried to run my app from Xamarin Studio on the same iPad, I got an error during the build.

TO FIX: In XCode, change the text of the bundle identifier manually to something else at the end. For example, my old one was "com.Mika.calc" and I changed it to "com.Mika.calc-" just by adding a space at the end. Immediately, a message will appear in XCode below the box you typed the text in that says "no matching profiles matching the bundle identifier were found," and below that there will be a button labelled "Fix Issue." CLICK THAT.
Now, copy the new bundle identifier and paste it in the Info.plist file of your project in Xamarin Studio. Now, when you go to [yourProject].iOS > Options > iOS bundle signing everything should be fixed.

No, you have to change all the places the bundle identifier appears at. Forgot to mention that little step. Also, if it doesn't appear to work at first, I tried cleaning the solution. After that it usually works.
I had to clean when I was changing the target and minimum Android versions in the [project].Droid options too for it to work. Generally, when I'm in doubt I clean the project just to see if that alone will fix anything first.

The way I solve was create an empty app with the same name, same bundle identifier, in xcode, I run the app to the iphone, then return to visual studio and link to the provisioning profile in ios bundle secction, and run to divece

@jimra said:
The way I solve was create an empty app with the same name, same bundle identifier, in xcode, I run the app to the iphone, then return to visual studio and link to the provisioning profile in ios bundle secction, and run to divece

Fantastik !!!! You saved my life !

Warning... If your Visual Studio compilation seems to be long... Look in your mac. System ask you to allow Visual Studio to Sign your app.

I am having a similar issue. I created a sample app in Xcode and ran it to my iPhone device fine. I try it in Xamarin and error. I have the bundles the same so not sure why it works in Xcode and not Xamarin.

I have tried all the above and I am still getting the following error:

Installing application bundle 'com.ravenworx.pricescanner' on 'Stephen Hunter’s iPhone'
ApplicationVerificationFailed: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.5muxvP/extracted/PriceScanner.iOS.app : 0xe8008016 (The executable was signed with invalid entitlements.)
error MT1006: Could not install the application '/Users/stephenhunter/Documents/Development/PriceScanner/iOS/bin/iPhone/Release/PriceScanner.iOS.app' on the device 'Stephen Hunter’s iPhone': Your code signing/provisioning profiles are not correctly configured. Probably you have an entitlement not supported by your current provisioning profile, or your device is not part of the current provisioning profile. Please check the iOS Device Log for details (error: 0xe8008016).

Application could not be uploaded to the device.

UPDATE
I fixed this by going to the Entitlements.plist and unchecking the "Enable Keychain Access Groups", then it ran on my device like a charm.

This process is ridiculously complicated. I am not a Mac person but can get around it. I have created an account and have the certificate and it is in my login on my key chain and it is in the project file on the Windows machine with Visual Studio 2017, building a Xamarin application. Trying to compile for an iPhone, simulator stuff works fine, when compiling so I can deploy to testers get this error about provisioning file. Again have done everything mentioned about on the MacBookPro which is doing the compiling and when I miss type the certificate name on the windows machine it sees the error, etc. but when I compile I still get the No Installed Provisioning File. The X-Code application (sample) which I created has a different name than the project file I am working Windows and VS 2017. Somebody please give me step by step on this. Wasted too much time. Thanks. Don

The above assumes you are a member of the paid Apple iOS developer program. It sounds like you may be using the free provisioning option? If so I do not think that will work for any device other than your own device. If you want to deploy to testers you will have to join the paid iOS developer program. If you have already paid for the iOS developer program, then the steps in the above linked guide should work.The way you mentioned XCode and the project name in XCode is what makes me think you may be using that free option, thought not nearly 100% sure.

@MarkFuriate said:
It is this kind of convoluted, controlling, asinine crap that makes me despise Apple. I would burn all of my Apple devices if I did not have customers that want iOS applications.

I am having huge problems with this too and I cannot seem to find a solution. One thing keeps leading to the other and I've spent about 4 hours today trying to get a test application to build on my phone, and so far nothing has helped.

Total and utter wind-up. All that I read says that I SHOULD NOT NEED any provisioning profile to deploy on the simulator - this is only required to deploy to a physical test device. If everyone would only use Android life would be so much easier!!

iOS Bundle signing is set to Developer (Automatic), provisioning profile also to Automatic.

On XCode on the mac, I can build and run a 'hello world' app in the simulator fine.

Now thinking that I need to ditch Xamarin and just do two apps natively - the time consumed working around all of Xamarins own issues exceeds the time required to build separately for two platforms making Xamarin totally pointless!

In case someone else comes across this issue while deploying to the iPhoneSimulator, the solution was to remove (eg blank out) the 'Custom Entitlements' field under MyProject.iOS --> Properties --> iOS Bundle Signing. This is where you give your app certain entitlements - eg Siri, Push notifications - which obviously wont work when running under the simulator. A more helpful error than 'Error: No installed provisioning profiles match the installed iOS code signing keys' would have helped here eg 'specified custom entitlements invalid while executing on iPhoneSimulator' - or simply ignore this field when running on the simulator?