Skip to main content
stolennickname
stolennickname
Inspiring
December 27, 2013
Answered

AIR 4 iOS 7 ipa won't install

  • December 27, 2013
  • 1 reply
  • 2763 views

I'm working on an iOS 7 application, built with AIR 4.0.0.1390, and am having a problem getting the ad-hoc ipa to install on my test iPod touch 5th gen iOS 7.0.4 device.

I can successfully get the app to debug on computer using the emulator, and can successfully package an ad-hoc ipa, but when trying to copy it to the iPod touch using iTunes sync, the app gets "stuck" in a strange last stage "installing" phase. A darkened icon of the app appears on the springboard, with the text "Installing…" below it. The top-level progress indicator in iTunes completely finishes sync/install progress, the app listing on the left has a button next my app that reads "Installing." Eventually this text changes to the name of the application, but the icon remains in the darkened state. When tapping on the icon at this point the text changes to "Waiting…" and the app refuses to launch.

I've built the ipa multiple ways, including with adt via command line, and have tried using the new AIR 4 -useLegacyAOT no setting.

The Console shows nothing too strange, other than a number of MDCrashReportTool could not remove remote path at ./DiagnosticLogs/security.log messages (which is a fairly common and known bug with iTunes, and should be unrelated).

The provisioning file is accurate and contains my correct device identifier.

The application is not using any ANEs.

What could be the problem?

This topic has been closed for replies.
Correct answer Colin Holgate

If you go to the iOS portal at developer.apple.com, does the provisioning profile show as being valid?

If you edit the profile there, which certificate is is using? Make sure that’s a distribution one.

1 reply

Colin Holgate
Colin HolgateCorrect answer
Inspiring
December 28, 2013

If you go to the iOS portal at developer.apple.com, does the provisioning profile show as being valid?

If you edit the profile there, which certificate is is using? Make sure that’s a distribution one.

    stolennickname
    stolennicknameAuthor
    Inspiring
    December 28, 2013

    Thanks Colin for the jolt. It's now working! I was mistakenly using a development provisioning profile when I should have used a distribution profile.

    Boy, managing certificates and provisioning can be tedious.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices