Frage

Ich habe eine Arbeits-App.Ich habe gestern von Xcode 4,2 bis 4.3 aktualisiert.Und ich habe mein Telefon von iOS 5.0 bis 5.1 aktualisiert.

Ich baue meine App in Xcode 4.3, und während sie angeschlossen ist, funktioniert die App auf meinem Handy gut.Ich lösche dann die App von meinem Telefon, erstellen Sie ein Ad-hoc-Ausschüttungsunternehmen in Xcode, lösche das neue App- und Distribution Provisioning-Profil in iTunes, und teilen Sie an, wenden Sie sich an iTunes Sync.

Die App überträgt auf mein Handy, und ich sehe es "installieren ...", aber dann wird es auf die sehr hilfreiche Meldung angezeigt.Ich habe versucht, ein neues Vertriebsprofil erstellt, aber keine Hilfe.

War es hilfreich?

Lösung

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

Andere Tipps

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.

Lizenziert unter: CC-BY-SA mit Zuschreibung
Nicht verbunden mit StackOverflow
scroll top