I've developed a number of apps for the iOS devices, and now I'm doing freelance work for other companies as well. We're at the point of getting all the certificates created, and I'm not clear on the right steps to take.
I've been invited -- and joined -- the client's Development Team in the iOS Provisioning Portal. There is no Development Certificate for me, however.
Do I need to go through the entire process again to get a new certificate issued, or is there a way to "reuse" the existing certificate I've already got.
You'll have to have a new development certificate generated by this Development Team you've joined; dev certs are not transferable in that way.
The "entire process" really isn't much: Use the Keychain to generate a certificate signing request, and then upload the CSR to the portal and wait for an administrator in that development team to approve it. Then download your new certificate.
I suppose it might be possible to re-use the same CSR that you used to generate your old certificate, but there'd be little benefit (you'd still have to upload the CSR and wait for a new certificate) and it might cause a lot of future confusion. Not worth bothering.
Related
I noticed when requesting development/production certificates for app development in App Store Connect that the production certificate presents with our company name while the development certificate presents with the specific employee who requested the certificate and put in their email in the Keychain process (Request a Certificate from a Certificate Authority...) Is this by design? Is it possible for the whole development team to share both a development and production certificate? I'm busy setting up a build machine for an iOS app and would like the development certificate to be generic for the whole team if possible.
Googled to no avail.
I want to know that if I revoked my Developer and Distribution certificate and obtain new one it'll affect to my Existing App.
No. It will not affect it/them. You use this certificates to just to sign the apps when submitting to review.
I have not seen this happen when I have revoked my certificates for debug and dist. From my experience, Apple checks your certificates when you submit the app, but not every time it's installed. If you have anything in AdHoc distribution, that would be affected as every time an AdHoc app is installed it checks that cert. Users wouldn't be able to install the adhoc with the now invalid adhoc cert. Recompiling ad-hoc builds with a new cert should solve that problem.
There are several similar questions here, but none could answer my basic question:
Is it possible to have two separate developer certificates in the keychain and two corresponding distribution profiles in Organizer?
I have my own (working) developer certificate and provisioning profile for my own iPhone apps.
Now I finished a project for a client and would like to use his developer account/certificates/provisioning profiles to submit his app to the app store on his account.
Is that even possible?
So far I downloaded and installed his certificates and they show up in my keychain, and I installed his provisioning profile in Organizer, but Organizer tells me "A valid signing identity matching this profile could not be found in your keychain.".
Likewise, the archive build fails.
I couldn't find a way to tell Organizer to use the certificate of my client instead of my own-I think this is the problem.
Thanks for any help!
Yes I've produced app store builds of projects for clients several times using their distribution certificate. No need to use their developer certificate. There are many things can could go wrong here, if you have access to the client's account you can go on to the provisioning portal and check things out:
make sure the bundle ID in the project settings exactly matches the app ID on the iOS provisioning portal (com.company.appname usually)
make sure the app store distribution provisioning profile is marked as "valid" and shows up under the distribution certificate.
make sure the app store build config in xcode references the client's distribution cert.
open your keychain and make sure that the client distribution cert also has its accompanying private key. This may be the problem, it's the part usually left out. The client must export his private key for his dist cert and send it to you in the .p12 file along with the password to the .p12 file. The dist cert can't be used to sign the app without the private key!
sometimes just quitting Xcode and restarting it helps.
See this solution to duplicate certificates: http://tapadoo.com/2012/certificates-magically-re-appearing-in-your-keychain-try-this/
The gist is that if you have an old private key and provisioning profile around, you can run into a case where Xcode will re-create an old certificate in your keychain. This will make code signing gag because it requires a single certificate with a given name. Deleting the old private key will resolve this issue.
EASY MODE
(I hate these archaic export errors so bad. So many hours wasted. I'm not religious but I still pray this helps you)
Log into https://developer.apple.com
go to Certificates, Identifiers & Profiles
bottom left: Provisioning Profiles
Delete any duplicates / invalid profiles (in my case I only had one but it was invalid)
Note: if you're trying to export an archive, you can leave the export window open, delete a provisioning profile, then click "retry" or whatever the button says. This will save you from have to re-archive over and over
#xcode8.2.1 #osx10.11.6
I have one big problem. I am having iphone developer account and now i have given all the controls to my developer so he has created certificate in account and install it. But he didn't know that if we want to use this information on multi system then we need to keep .p12 certificates and we have to install this certificates on another machine.
We don't have this .p12 certificate and we want to use another machine so what should i do for this things?. How can i delete current certificate from account and create another CSR and certificates for all machine?.
If anyone knows then please drops some line.
Thanks,
iPhone Dev.
If you still have the machine he created the Certificate Signing Requests (CSR) on, then you can export the private key from Keychain Access. Just find the key and export it.
If the private key is no longer available then you need to revoke the existing certificate and create a new one again. There are plenty of questions on Stackoverflow about this, e.g.
Lost Private Key For iPhone Distribution Certificate. What could be solutions?
I released an iPhone app - since then, my macbook hard drive died, and I hadn't backed up the signing certificate.
I see in the dev portal there's a way for us to revoke our current certificate. If I do that, will that make my current application already being sold, invalid? I don't plan on releasing any more updates for it, I just want it to sit up there and continue selling. I'd like to then create a new certificate so I can continue developing.
Thanks
Revoking your certificate will cause your app to stop working.
You can re-download the certificate on Apple's developer website.