After using a website app developed by a third party, many friends don’t know how to apply for a certificate and how to upload it to the app store. When the author originally uploaded it, I also read a lot of articles. Later I found that some articles were older and the app store development platform had been updated. So in my latest upload, I recorded the process and prepared this guide. This guide is now applicable to applying for certificates on the app store developer platform after 2014.
Prerequisite preparation:
1. You need to have a developer account in the app store. If not, please go
https://developer.apple.com/register/index.action
Apply. When applying, you need to pay attention to choosing the ios platform. After application, you need to pay US with a credit card. RMB payment is now supported.
2. You need to have a PC with a mac system, or install a MAC OS on a virtual machine, and confirm that you can connect to the Internet.
First, let’s briefly talk about the process of applying for a certificate (these processes will be explained in detail later):
The first step, iOS distribution certificate under certificates
This certificate is equivalent to the developer's certification, which can be a company or an individual.
Step 2: Apply for APP IDs under identifiers
This is equivalent to the application for the unique identification ID of the app.
Step 3: Apply for the push certificate under certificates
This certificate will correspond to the ID generated in the second step, which means that the push certificate corresponds to the app.
The fourth step is to apply for provisioning profiles.
This configuration file will select the certificate from the first step and the ID from the second step. Both must be related.
Detailed process graphic explanation:
The first step is to log in to the developer platform and select the certificate option. See the figure below for details.
https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa
In the second step, after selecting certificates, go to the certificate tool page. Here you can apply for a certificate for testing or a certificate for production mode. Here we talk about the certificate application process in the officially launched production mode.
The third step is to click the + sign to add a certificate.
Step 4: Select the certificate type
The fifth step is to make a scr file on the mac to generate the certificate.
Find [Keychain Access] in [Utilities] of the Mac's LanchPad interface
In the Certificate Assistant menu, select "Request a certificate from a certification authority"
Fill in the information as shown in the picture.
After saving to disk, you can see this file format certSigningRequest, which is the CSR file mentioned above.
Step 6: Go back to step 4 and proceed with the next step. Select the CSR file you just generated to upload. Used to generate certificates. After uploading, click Generate
When you see a download button appearing after generation, click to save the certificate. But it’s not over yet. Next, you need to use this certificate to generate a p12 certificate before it can be used for app generation.
Step 7: Double-click the cer certificate you just downloaded. This certificate will be imported into the mac system. In [Keychain Access], select My Certificate, and you will see the iphone distribution certificate you just imported.
Right click on the certificate and select export iphone distribution certificate
After exporting, it must be a p12 certificate, remember. If it is not P12, check to see if you have not exported it from "My Certificate".
When exporting, set a password to read the certificate to protect the certificate information. This password needs to be remembered and has a certain complexity. This password is needed when generating the app.
At this point, the iPhone publishing certificate has been created. If you do not need to push the certificate, you do not need to do the following steps to push the certificate.
Next, generate the APP IDs under the application identifiers. Please see the process below.
Step 8: Apply for APP IDs under identifiers
Select app ids under identifiers on the left
Fill in the name of your app id. English, usually just the English name of the website is enough
There is also a more important bundle id, which is filled in as shown in the figure.
If there is a push service, you can check push notifications
The application for app ids is over. This step is still very simple. This way your app will have a unique ID. Apply for multiple IDs for multiple APPs.
The next step is optional. Apply for a push certificate. If your app has this service, you must apply for this step. The steps are similar to generating a publishing certificate.
Step 9: Similarly, we select production under certificates. This is to generate the official certificate. If you are in the development period, you can choose development.
The bundle id just generated is used here to bundle the push certificate to this ID.
Step 10: Just like generating a publishing certificate, select the CRS certificate generated initially. Didn't you forget where you put it?
The next steps will be very familiar.
Also generate the cer certificate, and then import cer into keychain access.
After importing, you will see a certificate for app production IOS push.
Right-click to export the p12 certificate.
The above push certificate is completed.
The last step is to generate the configuration file.
In the eleventh step, select the app store configuration file under distribution in provisioning profiles.
After continuing, you also need to specify the IDS corresponding to this configuration file.
Then select the corresponding generated publishing certificate.
Finally generated. It's OK to save it locally.
Looking back now, 3 files were generated.
A release certificate, a push certificate, and a configuration file.
When regenerating the app, put these 3 certificates in and it will be OK.
The remaining pem certificate is produced as follows:
You need to use the previous push certificate.push.p12 and put it in any location. Now take the desktop as an example.
Open Terminal, enter cd desktop, switch to the desktop
Run in order
openssl pkcs12 -clcerts -nokeys -in push.p12 -out pc.pem openssl pkcs12 -nocerts -in push.p12 -out pd.pem cat pc.pem pd.pem > p.pem
In the end p.pem is what you want
This siteOriginal articleAll follow "Attribution-NonCommercial-ShareAlike 4.0 License (CC BY-NC-SA 4.0)". Please keep the following tags for sharing and interpretation:
Original author:Jake Tao,source:"Anmi Push Certificate Generation Guide"
