I have recently created a new certificate for my own profile but there are already development and AdHoc provisioning profiles exist. So now I want to include my newly created certificate into those provision profiles.
In Apple Developer portal I could edit "Development Provision Profile" and tick my certificate to include it into that provision profile but I do not see such option for AdHoc profile.
So my question is, can I include my newly created certificate into the existing AdHoc profile?
Because currently when I try to manually sign my project I get this warning in Xcode:
Provisioning profile "match AdHoc com.example" doesn't include signing certificate
"Apple Development: My Name (some_code_here)".
and when I click on info button I get this:
Doesn't include signing certificate "Apple Development: My Name (some_code_here)"
Any idea how can I fix this?
By mistake I removed the existing developer provisioning profile. So I am trying to create a new developer provisioning profile but each time it is showing ineligible.
Role of my user in the team is agent. App id, adhoc, and distribution provisioning profiles are created under that team with my ID which is working fine. I downloaded all developer and distribution certificates also. But in my keychain I found private key missing for the developer certificate but present for distribution certificate.
At the time of creation of the developer provisioning profile I am selecting all the available signing certificate and all the device ids. In my Xcode project when I am trying to select the developer provisioning profile, which is showing ineligible, I am getting the error message:
"Provisioning profile 'dev_provisioning_profile' doesn't include signing certificate 'iPhone Developer:'. No certificate matching 'iPhone Developer: ' for team 'team_name'.
What should I do to create valid developer provisioning profile?
Finally solved the issue. Just writing the steps. Not so sure that these are the exact steps but worked for me, may be helpful to others-
Delete the developer certificate that does not have a private key.
Then first check then uncheck the Automatically manage signing option in the project settings with selecting team.
Select provisioning profile in the project settings.
Delete the provisioning profile from machine.
Sign in developer account and edit the provisioning profile selecting all available developer certificates
Download the provisioning profile and add to XCODE.
By following these steps the provisioning profile becomes eligible and working fine.
You should delete the developer certificate that does not have a private key especially if there are multiple instances with the same identity. Also an easy way to solve this may be to uncheck then check the Automatically manage signing option in the project settings.
I have a distribution provisioning profile in the portal, say MyProvisioningProfile.
After going into Preferences/Accounts and clicking the refresh button I can see the provisioning profile fine.
When I produce an archive, Xcode creates a different provisioning profile named XC: .
I think that's the reason why I get the message 'No matching provisioning profiles found for My.app" and I click the Validate button.
How can I force Xcode to use the provisioning profile as defined in the portal instead of creating a new one?
ERROR ITMS-90161:"Invalid Provisioning Profile
I have created IPA using Xamarin IOS in ad-hoc mode and selected a adhoc provisioning profile. but while uploading, following error annoying me :(
when I uploaded using application loader:
ERROR ITMS-90161:"Invalid Provisioning Profile.The provisioning profile included in the bundle x.x.x.x[Payload/x.x.x.app] is invalid.[Missing code-signing certificate.] For more information,visit the iOS developer Portal."
If you get this error, you probably don't have the correct type of Provisioning Profile. There's a few types of Provisioning Profiles, most notably are the "Development" and "Distribution" profiles. I suggest looking at your provisioning profiles, and if necessary recreate them.
To elaborate: You have 1 Certificate (created via Xcode Certificate Generating). With this Certificate, you can create an "App Identifier", and Provisioning Profiles. You can use the same Certificate for both a Developer Provisioning Profile and a Distribution Provisioning Profile. They don't work with one another, meaning a Developer Provisioning Profile won't work for a release build, and a Distribution Provisioning Profile won't work for a debugg build.
Try this, and see if that helps. Be sure to haul the new profiles in Xcode (or any other method you'd use) and edit your project's settings.
Good luck!
Love and regards,
Björn
My issue was related to having Xcode Automatically manage signing. What finally fixed the issue for me was going into the developer portal, selecting Certificates, and revoking the Distribution Managed certificate. I then rebuilt my project in Xcode, keeping the checkmark enabled to Automatically manage signing, and a new Distribution Managed certificate was automatically created in the developer portal under certificates. Distributing the archive to the App Store no longer produced any errors.
This issue also came up in other projects where I manually manage the Provisioning Profile. What worked for me was doing the following on the developer.apple.com portal:
Revoke the existing Distribution Certificate linked to the app's provisioning profile.
Issue a new Apple Distribution Certificate.
Link the new certificate to the app's provisioning profile.
Make sure to select the correct provisioning profile for your app's target in Xcode.
While de3z1e's solution seems to work for most people, it did not work for me. What did work was creating an Apple Distribution cert when using XCode settings. While Xcode is open,
Go to preferences (Command + ,) -> Accounts -> Choose your team -> Manage certificates -> + (bottom left) -> Apple Distribution -> Re-archive + upload
I am not sure why the other solution did not work for me, but this did. I also have Xcode manual signing on and left it on.
For Distribution:
If you upload to Test Flight you need an Apple Store provisioning Profile.
If you are distributing to specific devices, you need Ad hoc provisioning profile.
You assign it in visual studio through Manual Provisioning, choosing an Apple Distribution Identity, and choosing your provisioning profile manualy - nothing in automatic.
If you like me could not find your newly created provisioning profile to appear in visual studio, make sure the bundile indetifier in info.plist is the same as used in the provisioning profile.
If you are white-labeling as per xam-girls blog, other copies of info.plist is not looked at by visual studio iOS Bundle Signing
I faced same problem. I edited profiles, it works.
Click edit button all provisioning profiles and save it. Download and use edited profiles. App will upload to store.
I received a complete Xcode project from another developer. I can run the app in the simulator but I get the "No matching provisioning profiles found" error message when trying to compile it to my iOS device.
How can I get this to compile to my device? Changing the provisioning profile to my own under build settings doesn't work.
This error mean your provisioning profile is wrong. Check your provisioning profile installed and certificate are right. Check if your device is register for this provisioning profile too maybe you didnt add it to your provisioning profile