Non-IDP universal certificate real machine test, swept all SDK versions!

Two days ago, in order to test my app on the device, I searched for various methods for Certificate-Free debugging on the Internet (because I am not an IDP), but the results were quite satisfactory, none of them are spared. Later, A friend gave me a method to sign the certificate with a certificate of 10 thousand, and then we could test it on the device directly. It was awesome! The following is a graphic Tutorial:

 

 

I. First install the certificate!

Double-click hujunling. p12. Then, the system prompts you to enter the password. Just click it and there is no password! Immediately, the certificate is installed.

 

 

2. Open the Special. mobileprovision file and click provisioning profiles on the Left bar. If you see the following interface, congratulations, you have succeeded 80%. The certificate is successfully installed and can be used. But if special has an exclamation point warning! In addition, if the following error is reported in red, it is likely that your xcode has been cracked before (because there is a method on the Internet to crack xcode for real-machine testing). I tried this method, the certificate cannot be installed. No more. reinstall xcode!

 

3. After installing the certificate, we need to modify several configurations in the specific project of xcode. It is very simple and fast, so we can run it on our device happily!

First, modify the project Info and double-click the project.

 

Make sure that the project format is above 3.1. Generally, 3.1 is selected.

 

 

 

In bulid, select the certificate we just installed in code signing identity. Do you still remember the name?

Next, modify the target version of IOS deployment target. Here, the version should not exceed your device system version, and remember this version, it will be the same when we change the parameters of another file!

 

 

Now, the info of the project has been changed. We need to change the info of targets. Double-click.

 

 

Find code signing identity and select our certificate. Note that this is no longer the info configuration file.

 

Next we will find the IOS deployment target. Pay attention to the version of IOS

 

These two info parameters are the same, right? Next we need to change a different place. Continue in target info. Select the Properties tab!

In the second frame, identifier deletes the original content and changes the ID randomly. Yes, you are not mistaken. You can change the ID randomly. Here I will change it to Wewe. This is a universal certificate! Now, our journey is complete. Close info and connect to the device. Run it!

 

 

4. You may not be able to run after completing the above steps. This will involve many other factors, such as devices not found, memory errors, and not all images are in PNG format (this is a strange phenomenon? If the image is not in PNG format, it may fail to run !) And so on. At that time, we had to solve the specific problem!