I have developed an iOS app for my corporation. We distribute it via AirWatch. Some of the certs are going to expire soon and it is SO confusing to try to figure out what to do. I have googled and it seems every page has different information. I would really love it if someone could point me in the correct direction.
I have an "iOS Development" cert with my name on it. It appears that I cannot renew it, only revoke or download. Some pages said if I download it again it gets updated, some say I need to create a new cert. Which one is it, and do I do this in Xcode or on the portal?
I have an "APNs Production iOS" cert with my company's id on it(the reverse dns thing, like "com.apple.mobile". It is also due soon. How do I renew, and where do I renew it, in Xcode or the portal.
We do not use Apple Push Notifications in the app, but I am under the impression that you still need this as it is the way Apple securely identifies your app. Is this true?
I have a "iOS Provisioning Profile" that will also expire. Same questions. Can I just edit it to renew it? Do I do this in Xcode or Portal.
Thank in advance.
Yes, you will need to renew your profiles (all that you are using for development or distribution. Then, you will need to re-build any apps that were built with the old profiles. Otherwise, no one will be able to install the app that was build with the expired profile. Basically, any apps built and distributed with an enterprise distribution profile will need to be re-built at least once a year.
Edit: more details on how to generate a new certificate.
Just go the the ios developer portal, and go to the area on the right for Certificates, Identifiers, and Profiles on the right. Go to the Certificates area, and click the + icon to generate a new certificate. Follow the instructions there for generating the new cert. Once you have your new cert, go to the profiles section, and you will need to re-generate your profiles with the new cert. For each profile, click the edit button, change the certificate dropdown to your new certificate, and then click the Generate button. Download the new profile, and use it to re-build your apps.
Related
I am trying to implement APNS for my App and am hitting a wall while trying to generate a provisioning profile. I followed the instructions to create an APP id and was able to generate an SSL certificate for my App (the type is shown to be APNs development IOS). However, when I try to generate a provisioning profile, following the screen where I choose the AppID of my app, I do not see the SSL certificate I generate for this app. In the certificates list, I only see a certificate of type 'IOS development' that was created previously. I have been stuck on this issue for a while. Can someone please help?
Thanks
I resolved my own query. we need to add iOS development certificate while creating profile for APNS. You should have the p12 of that iOS development certificate.
The first time i uploaded an app to the app store i followed a youtube tutorial. Now i want to upload my second app. I have a lot of trouble understanding the process to upload an app. I've create a Provisioning profile, A certificate and a Distribution profile for my first app, am i supposed to use those again? Do i need to create a new provisioning profile, a new certificate and a new distribution profile? It's really confusing since i've been coding for less then 2 months.
Some step-by-step information would be very helpful. Thanks in advance.
The process is not as complicated as it seems
You need one developer certificate for testing and one distribution certificate for deployment (ad hoc or AppStore). If you have a valid certificate (given that you submitted an app already), then make sure you have it in your keychain (with the private key).
For a new app, you need to create a new appID. Remember that it should match the bundle identifier in your Xcode project.
With the distribution certificate and the appID, you can create a new distribution provisioning profile that needs to be downloaded to your machine. And should be used for the code signing in Xcode.
So, short answer. Use you current (valid) distribution certificate, add a new appID (matching your bundle identifier) to create a new Distribution Provisioning Profile. Use the profile to code signe your project.
Good luck... enrique
Definitely you need another provisioning profile connected to new APP ID for your second app
You dont need a new certificate though you need separate Appstore distribution provision profile.
Before creation of provision profile, you need to create APP ID.
After new APP ID you need to create new provision profile, you would be asked for select distribution certificate and you can select previous one there and also would be asked for APP ID and there you need to select your second app id (not older one).
Please check Apple Distribution Guide. It has clear instruction to do so.
And you can also checkout this tutorial. It may help you.
I've tried to do App Store Submission, it couldn't be completed as the error
show "No identities are available for signing".
I checked out from the forum and followed step by step, it still can't
fix the problem.
Do you have any idea?
Go to developer.apple.com, download the distribution certificate and install that on you mac. After that you will be able to sign your app.
Check to see if your Provisioning Profiles have expired. I already had distribution provisioning profiles created but they had just recently expired. The error message xCode was giving just said "No identities were available for signing" even though the private/public keys were correctly in the Key Store. To fix I just did the following:
From the iOS Provisioning Portal, select "Provisioning" on the left
Under "Provisioning Profiles" select "Distribution" (this is where I could see that the provisioning profiles had expired
Click on the expired Provisioning Profile
Click "Edit"
Select the Certificate you want to use for the Provisioning Profile
Click "Generate"
Click "Download"
Open the file (it should launch xCode and add it to the Organizer)
After this I was able to submit the update to the App Store no problem. They really need a better error message.
I'm at the point where I'm ready to submit an app - an Apple doesn't elaborate much on how to sign and submit apps. I have both the WWDRCA certificate and one I created but am at a loss on where to put them.. do I add them via drag n' drop into XCode? Why do I need the WWDRCA? Anyone have any info on this? Would be GREATLY appreciated
First, make sure you have correctly installed the Installer, Developer and WWDR certs in your Keychain.
In Xcode, edit your target build settings and under 'Code signing entity' and select your Developer certificate. Then build your app using 'Build and Archive'. Finally, open Organizer (via Window menu) to verify and submit your app.
At least, that's the theory. I agree that it's tricky. The Apple Developer Forums have several instructive postings about the potential pitfalls. Good luck!
Edit: Dang, I missed that it's about the Mac App Store, my post is about iOS... For the Mac App Store, there's also a document from Apple and a checklist with links. That checklist seems like a good starting point for all the relevant information.
Original iOS related post:
If you log in to the Provisioning Portal, Apple explains in detail how to get and use a certificate (now even with videos). Right when you login to the portal, see the right column. Or click on the "Certificates" link on the left and then on the "How to" tab. It's step-by-step guide with screenshots. Also, see the "Provisioning" section in the left meny, again click the "How to" tab. For submitting, see the "Distribution" section in the menu on the left. If you still have specific question after reading/watching that material, go ahead and ask.
You need the WWDR CA certificate so that your keychain and Xcode can actually validate your certificate. Certificates are signed by other certificates and form a chain of trust. But there has to be a start, and that is the CA certificate for which you first explicitly state "Yes, I trust this certificate" and thus all certificates that were signed by it.
This is also how your browser works with HTTPS: your browser comes with a bunch of CA certificates that it trusts by default, for example the CA certificate from Verisign. And if your browser then sees a certificate that was signed by Verisign it knows it can trust that website since it already trusts the Verisign CA.
I have a question regarding app submission.
Situation: We have an iPhone Developer account and our customer has an iTunes Connect account. Is it possible that we hand them the signed, zipped application (that is signed with a provisioning profile from OUR account) and they upload it on their account?
Or is it REQUIRED that they give us acces with the "technician" role?
From my first impression, i think it should be possible that both accounts are not in any way connected, but i am not sure.
Any help is appreciated. If it is possible, please post references, Thanks =)
I think the short answer to the question in the title is "No".
See the iTunesConnect > FAQs > Manage your applications
I sold my app to another developer and
can no longer distribute on the App
Store. Can I transfer the app to the
new developer's iTunes Connect
account? At this time, applications
cannot be transferred to another
developer account. If you would like
the application to be sold through
another developer account, you will
need to remove the app from sale in
the current iTunes Connect account and
upload the app under the new iTunes
Connect account.
Not exactly your question, but sounds similar enough.
We had a need to resign a 3rd party developer supplied app with our signing keys - which sounds similar to what you want to do:
1) Use Xcode's Build > Build and Archive feature to create the version of the app to had off to your customer.
2) Select that build in the Archived Applications source in the Organizer
3) Choose Reveal Archived Application in Finder from the contextual menu
4) Select and compress the enclosing folder
5) Send that zip archive to your customer.
Your customer would then unzip and expand that archive in ~/Library/MobileDevice/Archived Applications. That will make it available in the Xcode Organizer. Your customer can then use the Share Application… and/or Submit to iTunes Connect… buttons to re-sign and distribute the app using your customer's distribution provisioning profile.
EDIT: A follow up that may not be clear from the info above.
To be able to do this, the 3rd party developer needs to build the app with your development profile; e.g. they need to be a "Team Member" of your account. They can do nothing more than build the app and sign it with development keys. Then they can deliver a build that has been compiled with your development keys at which point you can re-sign this with your distribution keys and submit.
If you need to, you can remove them and revoke their information from the iOS Provisioning Portal after successful app deployment.
EDIT2: With the Xcode 4 .xarchive bundles, you can just copy the .xarchive bundle into ~/Library/Developer/Xcode/Archives/[date]/ folder. Then it will show up in the Organizer under the Archives section - validate, share and submit from there.