IOS 5.1とXcode 4.3にアップグレードされていると、アプリはインストールされません

Question

私は作業アプリを持っています。昨日Xcode 4.2から4.3から更新されました。そして私はiOS 5.0から5.1への私の電話を更新しました。

私はXcode 4.3で私のアプリを構築し、つながっている間、アプリは私の電話でうまく機能します。その後、私の電話からアプリを削除し、Xcodeで配布可能なAD-HOCを作成し、新しいアプリと配布プロビジョニングプロファイルを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.