Geek Answers Handbook

Updated to iOS 5.1 and xcode 4.3, now the application will not install

I have a working application. I upgraded from xcode 4.2 to 4.3 yesterday. ANd I upgraded my phone from iOS 5.0 to 5.1.

I create my application in Xcode 4.3, and, attached, the application works fine on my phone. Then I will remove the application from my phone, create an ad-hoc distributed in Xcode, drop the new application and distribution sharing profile in iTunes, and then tell iTunes SYNC.

The application is transferred to my phone, and I watch it “install ...”, but then a pop-up message “failed to install” appears. I tried to create a new distribution profile but did not help.

+8
ios xcode ad-hoc-distribution
source share
2 answers

This is what worked for me in Xcode 4.3.1

  • Go to Xcode
  • Open the project, click the project file in Explorer
  • In accordance with the targets, click on the project goal
  • Click on the "Build Settings" tab.
  • go to the "Code Signing" section
  • By signing the Identity code -> release -> select the hoc add profile created in the IOS provisioning portal (positions -> Distribution)
  • CMD - S (save)
  • Click on the project archive → and you can create your own additional
+7
source share

I had the same problem when I came across this topic. Melvin's answer above was what I already tried, and I was sure that was correct. Then I read a comment from Gary, saying: “At first, it didn’t work for me when I just changed the Release setting. I changed all the code signature identification parameters from Developer to Distribution, and then it worked.”

It turns out that Gary was corrected for me. But this is not a solution, but it indicates a problem with the root. In my case, this worked because my "Ad Hoc Distribution" scheme was not configured correctly. I suspect this applies to Gary.

Here is how I fixed it:

  • Select an Ad Hoc Distribution scheme (for example, use the Scheme button to select it)
  • Select "Edit Schema ..."
  • Select "Archive" in the left column
  • Select the correct "build configuration" in the selection box (for example, "Release" or "Ad Hoc" or whatever you called your Ad Hoc configuration).

In my case, I had an assembly configuration configured for the storage assembly configuration in the App Store. Thus, the archived version of Ad Hoc was signed for the App Store. Naturally, when I try to install it on a special test device, it will not be installed.

Melvin's answer is also needed to fix this. You must use the correct code identifier for your custom build configuration.

+4
source share

More articles:


All Articles