I used A's signing certificate to distribute the app before.Then changed it to B's signing certificate
It was successfully archived. I was stuck at last step which showed "Provisioning profile doesn't include signing certificate"
I can't delete all certificates cause there are other people use mac
Tried following solutions which are not working
In accounts and downloaded manual profiles
delete B's certificate in key access
Do anyone know
how to solve it? or how to update the signing certificate in Provisioning profile?
Thank you so much
Related
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.
When signed with a certificate which is not included in the provisioning profile, still app is able to install successfully on device,how ?
I have two wild card signing Identities
A
B
I created provisioning profile with Signing identity A
Now from command line i resigned it with B using the same provisioning profile.
App getting installed successfully, how ?
You need to understand that in order to run an app on an iOS device, you just need a valid provisioning profile.
You have two wildcard provisioning profiles, so technically both could work. However, you state that your provisioning profile was created with Signing identity A. First, confirm that your provisioning profile has only the Cert for identity A selected. Technically, a provisioning profile can be valid with multiple certificates.
If you confirm that your profile is not associated with the cert for signing identity, meaning the profile should not be valid if you signed the app with identity B, the other likely reason is that you already installed the app (or some other app) using the profile and signing identity A. If that is the case, there is a valid provisioning profile on the device that says your app should be allowed to run. I posted some more details about scenarios where the provisioning profile packaged with the app may be invalid / expired / etc. but the app will still run on the device in this post.
If you are expecting to use the code signing / provisioning profile to keep an app from successful install, you should have a dedicated, explicit bundle Id in your provisioning profile, along with a certificate specifically for that app ID. Then you can expire the profile and revoke the cert when you need to prevent the app from running on devices.
Edit: To check if this is due to an existing provisioning profiles, open Xcode, go to Window->Devices Right click on the device in question and select "Provisioning Profiles", like this:
If you want to try it out, you can remove all the provisioning profiles from the device and try to re-install. If you really only have a provisioning profile that is configured to accept the signing identity A, and you sign the binary with signing identity B, it should not work.
I'm having so many issues archiving and uploading my project to the apple store for submission. Probably have gone through changing the bundle identifier-- creating a certificate, updating the app ID and creating a provisioning profile 5 times already.
When I try to validate the project after I've archived it I get the error missing ios distribution signing identity for signing identity (Me)...
Is it because my iphone distribution says 'this certificate has an invalid user'? How do I fix that? I downloaded the certificate link they suggested and used it to create a certificate. Very stuck and frustrated.
Every time I try to change this section to be the iOS Distribution Identity and corresponding Provisioning Profile it says it's unable to find a matching UUID for the provisioning profile. Not sure if that's helpful but it seems like something is mis-configured, just not sure where to look or where to start over, or if there is some lurking configuration from an older mistake that is screwing me up.
delete all the certificates and provisions profiles, reinstall all the certificates and profiles. this might resolve the problem.
Update the apple developer certificate
1->Open keychain
2->Go to view - Show expired certificate
3->Delete the red mark certificate "Apple Worldwide Developer Relations Certificate Authority"
4->Download https://developer.apple.com/certificationauthority/AppleWWDRCA.cer
5->Install it and now see if you are able to use certificate or not
More detail explanation This certificate has an invalid issuer Apple Push Services
I have an app developed and working with our company's profile and distribution cert. I just recieved the .p12 from the company that we are going to be distributing to, and am trying to rebuild the app with their certificate. However, when I select 'Archive' I receive
"No unexpired provisioning profiles found that contain any of the keychains signing certificates"
I believe I'm missing something here, but google and I can't figure it out. Do I need a new profile with that certificate in it? If so how do I go about uploading the .p12?
Thankyou very much.
With the p12 you are enabling your computer to make releases for the outside company but what you need right now is the provisioning profile associated with that app (it will be specific if you have in app purchases or push notification otherwise it will be the default developer profile) and that .p12
Check out your keychain, distribution certificate has key. If not then install right certificate.
When I create a Development Provisioning Profile (to distribute the app Ad-Hoc) the organizer in Xcode gives the following error: Valid signing identity not found.
I tried the steps below to solve my problem without any luck:
remove all keys and certificates in my Keychain.
revoked my Development Certificate in the iOS Provisioning Portal
created a new Development Certificate
edited the Development Provisioning Profile for my app and selected my Certificate.
Xcode says my profile is valid for de Development Provisiong Profile.
created the Distribution Provisioning Profile.
Xcode says there is no valid signing identity found for the Distribution Provisiong Profile.
What other solutions can I try? There is already an app in the App Store publish by my colleague.
I'm using Xcode 4.4.1
This happen when you miss the private key of the certificate signer. You must have the private key in your keychain.
Usually when you request certificate from a certificate authority, it created a private key in your keychain, which subsequently used for creating all the provisioning profiles.
I think you are missing one important step. 'Request a certificate from certificate authority'.
Please have a look at this.