The solution of "applicationverificationfailed" problem appeared in the PP Assistant installation app

In an iphone, if a user installs some apps that will see a "profile" on the phone's settings-the bottom of the list, the online description file is an XML file that records some important information about a particular app, which is more important. I wrote this blog mainly to record a description of the document I encountered in the development of the problem, I hope to everyone and 6 months later I have some inspiration.

Problem Description:

The phone QAIphone6 for QA testing always fails when you install the app with the PP helper, prompting "applicationverificationfailed", while installing the app in the same way for other phones can be successfully installed.

To resolve an attempt:

Online Check, far apart said what is also there, see my dazzling, and the main solution is to say "jailbreak ...", that is, all for the jailbreak machine, but QAIphone6 no jailbreak ah, this is a bit worrying. So decided to use their own small 4 ramming drum. Because only the QAIphone6 installation failed and the other installation was successful, the target was positioned on the QAIphone6 "configuration". Inadvertently saw the small 4 settings inside the "description file" column, there is "Inhouse_for_any", this is not the provisioning profile I used to pack, so:

① deleted the description file and then deleted the previously installed app and installed it through the PP helper. As expected, this time the installation failed, and the prompt message is "applicationverificationfailed".

After ②, I ran through Xcode directly on the small 4, and found that the "Inhouse_for_any" was installed on the small 4. Then delete the app, through the PP Assistant to install the app again, this installation success.

Through the above two experiments to guess: whether the app can be installed through the PP assistant to the "description file" must have a big relationship.

To solve this problem, I researched the next Xcode and found that it was easy to install the provisioning profile used by the project to the phone via Xcode. The steps are as follows: (The following example shows only the specific steps, not the "Inhouse_for_any" mentioned above)

(1) Find the corresponding provisioning profile.

In fact, the provisioning profile shown in the Xcode project is a file with the extension mobileprovision.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/72/3C/wKioL1XfBALyKIb1AACA6dLfEO0318.jpg "title=" Qq20150827-4.png "alt=" Wkiol1xfbalykib1aaca6dlfeo0318.jpg "/>

In order to find the specific file corresponding to Layne3, the following methods can be used:

① Top Xcode->preferences, select the Account tab in the popup dialog box, such as:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/72/40/wKiom1XfAmyzm3OLAAGo6_gd8q0197.jpg "title=" Qq20150827-5.png "alt=" wkiom1xfamyzm3olaago6_gd8q0197.jpg "/> If no account is currently available, use the + sign in the lower left corner to add your developer account, as shown in the add-on.

② Select "View Details" in the lower right corner and the following dialog box appears:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/72/40/wKiom1Xe_3qjs05PAAGxEmPkl6k720.jpg "title=" Qq20150827-1.png "alt=" Wkiom1xe_3qjs05paagxempkl6k720.jpg "/>

At this point below the dialog is all the provisioning profile files associated with this developer account, click on the mouse on the Layne3, select "Show in Finder" to open the corresponding folder to view the actual. mobileprovision File:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/72/40/wKiom1XfAAyQGzXlAABYavIDBKs415.jpg "title=" Qq20150827-2.png "alt=" Wkiom1xfaayqgzxlaabyavidbks415.jpg "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/72/3C/wKioL1XfAkqhuH6wAAF96A15FRg202.jpg "title=" Qq20150827-3.png "alt=" Wkiol1xfakqhuh6waaf96a15frg202.jpg "/>

In fact, this mobileprovision file is under the ~/library/mobiledevice/provisioning Profiles folder, but the name is messy, The general user directly into this folder is unable to directly find their own needs of the mobileprovision, this will be a manual work, but also technical work. Once found, we copy it to the desktop.

(2) Install provisioning profile (ie. mobileprovision file) to the phone

Connect your phone to your computer and select devices under the top Window menu of Xcode, such as:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/72/3C/wKioL1XfBauCBHPYAAEEJW-kxXk505.jpg "title=" Qq20150827-6.png "alt=" Wkiol1xfbaucbhpyaaeejw-kxxk505.jpg "/>

In the popup dialog box select the specific device, right click on the mouse and select "Show Provisioning Profiles",

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/72/40/wKiom1XfBArTwaSpAAIsHO0r6-8610.jpg "title=" Qq20150827-7.png "alt=" Wkiom1xfbartwaspaaisho0r6-8610.jpg "/> will pop up a new dialog box,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/72/40/wKiom1XfBH-wT5InAAJdEaHZOsE788.jpg "title=" Qq20150827-8.png "alt=" Wkiom1xfbh-wt5inaajdeahzose788.jpg "/>

In this dialog, users can easily add or remove provisioning profiles from the lower left corner of the + and-to the phone.

Add the corresponding provisioning profile for the phone and then install the app via the PP helper.

Attention:

In the process there is one more thing to note, that is, some phones even if you install provisioning profile, the phone's settings-the general does not display the "description file" column (at least my 5s is this), the specific reason is unclear. Therefore, in order to see if a phone is installed with provisioning profile, the above mentioned method should be the most reliable.

This article is from the "Layne Learning Corner" blog, please be sure to keep this source http://laynestone.blog.51cto.com/9459455/1689068

Original address: http://laynestone.blog.51cto.com/9459455/1689068

The solution of "applicationverificationfailed" problem appeared in the PP Assistant installation app