iOS 5.1 및 Xcode 4.3으로 업그레이드, 이제 앱이 설치되지 않습니다.

Question

나는 작동 앱이 있습니다.어제 Xcode 4.2에서 4.3까지 업데이트했습니다.그리고 iOS 5.0에서 5.1로 휴대 전화를 업데이트했습니다.

Xcode 4.3에서 내 앱을 빌드하고 묶여있는 동안 앱이 내 전화로 잘 작동합니다.그런 다음 내 전화에서 앱을 삭제하고 Xcode에서 배포 할 수있는 광고를 만드고 새 앱 및 배포 프로비저닝 프로필을 iTunes에 넣은 다음 iTunes에게 동기화하십시오.

앱이 내 휴대 전화로 이동하고 "설치 ..."를 보면서 "설치 실패"를 팝업합니다.나는 새로운 배포 프로파일을 작성했지만 도움은 안된다.

Answer 1

This is what worked for me in Xcode 4.3.1

• Go to XCode
• Open the project, click on the project file in the explorer
• Under targets, click on you project target
• Go to the "build settings" tab
• go to the "Code signing" section
• By code signing Identity -> release -> select the add hoc profile you created in the IOS provisioning portal ( provisions -> Distrubution )
• CMD - S ( save )
• Click on project -> archive and you can create your add-hoc

Answer 2

I was having exactly the same problem when I came across this topic. Melvin's answer above was something I had already tried, and I was sure I had it correct. Then I read the comment from Gary saying: "At first this didn't work for me, when i only changed the Release setting. I changed all of the code signing identity settings from "Developer" to "Distribution" and then it worked."

It turns out that Gary's fix worked for me too. But it isn't the solution, but it does point to the root problem. In my case, it worked because my "Ad Hoc Distribution" scheme was configured incorrectly. I suspect that is the case for Gary as well.

Here's how I fixed it:

1. Select your Ad Hoc Distribution scheme (e.g., use the Scheme button to select it)
2. Select "Edit scheme..."
3. Select "Archive" in the left-most column
4. Select the correct "Build Configuration" in the selection box (e.g., "Release" or "Ad Hoc" or whatever you named your Ad Hoc build configuration)

In my case, I had the Build Configuration set to App Store Release build configuration. So the archived Ad Hoc build was signed for the App Store. Naturally, when I would try to install it on an ad hoc test device it would not install.

Melvin's answer is also essential to fixing this. You must be using the correct code sign identity for your ad hoc build configuration.