Skip navigation
swfisgood
Currently Being Moderated

itunes sync 'AppName' failed to install.

Dec 12, 2011 8:38 PM

I dont understand why i get this sometimes when trying to sync an app to my device (message shows on device itself)

 

certain provisioning profiles just dont work. I will usually fumble around, creating new ones until i get one to work.

 

The latest attempt:

I created the provisioning profile on the iOS developer site.

I included 2 udids.

downloaded

 

I created the app, it works on one device, but not the other

itunes sync 'AppName' failed to install.

 

ok, let me test again,  so i go create a new profile for just one UDID (the UDID that was working a moment ago)

itunes sync 'AppName' failed to install.

 

What!!! WHY!

Its like some profiles are corrupt or something? What can i be missing here?

 

for one example, both udids are in the profile, why would the .ipa install on one, but not the other?

(installing from 2 different comptuers)

 

 

 

 

 

 

 


 
Replies
  • Currently Being Moderated
    Dec 12, 2011 8:45 PM   in reply to swfisgood

    Hi:

     

    Are you installing through iTunes, or xCode? What is your iOS version? Can you also post the versions of all the tools you are using?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 12, 2011 8:47 PM   in reply to swfisgood

    You can expand IPA files and take the app file that is in the payload folder, and drag it straight to your device in the Organizer window of Xcode, without involving iTunes.

     

    What was the second device? If it was an iPhone, iPhone 3G, iPod Touch 1st or 2nd generation, or a 3rd generation 8GB, then AIR apps won't work on them.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 12, 2011 8:48 PM   in reply to Saumitra Bhave

    "iTunes" was in the subject, so I took it that he used iTunes.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2012 9:22 AM   in reply to swfisgood

    I am having the same problem. One of my developers created a Flashbuilder Actionscript mobile app which runs fine on the FB simulator but I can't install (for testing) it onto my iPad.  Do others have this problem? 

     

    I am a member of three different devleopment teams.  I'v eensured I am using the correct dev_certs - matched them to each team.

     

    I've matched my UDID, app_id to ensure I am using correct ones.  I can't upload ipa (at times) to TestFlightapp.com becuase of ubiquity errors - but then again sometimes it does load - but it will not install on iPad.  I also cannot install the ipa using iTunes.  I've loaded my .mobileprovision files via iTunes onto the iPad as some posts say you need to do that.

     

    I've never had problems using xCode testing on my devices but we can get anything created with FlashBuilder loaded.  I've created AS and Flex ipa files used my personal dev certadnmobile provisioning in addition to the above mentioned dev_certs/mobileprovision for my work team.

     

    Are otehrs having this same issue and how is it being resolved.  If we can't correct this we'll have to abandon FlashBUilder, learn ObjectiveC or do everything HTML5 based.

     

    Thanks,

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 19, 2012 4:13 PM   in reply to gigard

    I probably won't be much help but here's a hail Mary

     

    Could your provisioning profile be outdated? They expire after a year or less

     

    Is your profile installed using the iPhone configuration utility? I could find no other way to install it without the utility

     

    Are you using the correct bundle identifyier in your xml file? This is a common problem if you are making an app called foo_bar you might have a created a bundle ID at apple's site called com.foo_bar.myCompany yet apple does this number on it:

     

    af10234c.com.foo_bar.myCompany

     

    Remove the af10234c, don't put it in the bundle ID field in flash! Cause iTunes will say something like your profile is bad.

     

    I bet you can now appriciate how well though out error handling is on iTunes for developers . [sarcasm if you can't tell] Easy to use for everyone but the people that make the damn things work.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 23, 2012 3:25 PM   in reply to 12345abcdefghi

    Thanks 12345abcdefghi, that tip worked for me. Stupid as I was adding the actual string in the provisioning profile to the app.

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 27, 2012 2:12 AM   in reply to swfisgood

    I've got the same problem, my ID on the descriptor file is same as my Bundle ID but still it failed to install. Any ideas?

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 2, 2012 5:34 PM   in reply to swfisgood

    getting the same problem as well.. The app is working great with the ios_development.p12 and the development mobileprovision when I debug, but when I change to the ios_distribution.p12 and ad hoc mobileprovision (all created at the same time in the portal) it says "app failed to install" on all devices I have set under Devices and work with the developer version.

     

    I'm using Flash Buider 4.6 and Air 3.2 (did the same with 3.1), the devices are a iPhone 4, iPod Touch and a 3GS.

     

    Want to get this submitted asap, any help is most appreciated

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 3, 2012 1:14 PM   in reply to kcBZOR

    For what its worth (probalby not much) I was never able to test my distro.p12 compiled apps on my devices I just kinda winged it and sent the binarys to Apple hopeing I didn't goof up packaging the final version.. probably not what you want to hear...

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 3, 2012 6:34 PM   in reply to swfisgood

    ok I got it working.. my problem (I think) was that I was using the same .csr for the development and distribution certificates, you need to make a new .csr for each. ad hoc works and the app is off for review.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 4, 2012 1:02 PM   in reply to kcBZOR

    I've run into this issue a number of times during development. It is really agravating as it is not intuitive where the problem lies, but has always been solvable. This typicallly happens to me when I try to add a new device for testing.

     

    This is what I do that seems to work for me:

     

    - First you have to update ALL of your mobile provisioning files through the Apple Member Center site to include your new device (debug, ad hoc, release, etc). If you miss updating any one of these your app may end up failing to install. Then download all the new files.

    - You need to manually delete any old provisioning files that are associated with iTunes. Simply dragging the new files onto iTunes doesn't always seem to work for me (I think this is what causes the problem for may people). Instead on Mac navigate to ~user/Library/MobileDevice/Provisioning Profiles/ and delete the old *.mobileprovision files that you are trying to replace. Manually copy the new mobile provisioning files into this folder to replace the old ones. I'm not sure where the corresponding folder is located in Windows.

    - Remove the old profile(s) from your iOS device. Go to: Settings->General->Profile. Select the Profile(s) and then Remove.

    - Rebuild your app using the new mobile provisioning files.

    - Drag your new ipa file onto iTunes to replace the old ipa file.

    - Now sync again with iTunes.

     

    Hopefully that will get you back up and running again.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 26, 2012 7:58 PM   in reply to AirDoctrine2

    I ran into this issue and the problem was that I had changed the <id> and <filename> tages in the xml file.

     

    For some reason this did not cause a problem on an iphone 4s, but did prevent it from being installed on the 3gs. When I changed them both back, it worked on the 3gs as well.

     
    |
    Mark as:
  • Currently Being Moderated
    May 25, 2012 3:20 AM   in reply to swfisgood

    We had the same error msg when using a Development Provisioning Profile.

    Using FlashDevelop we followed the steps of Emanuele Feronato at http://www.emanueleferonato.com/2011/09/22/creation-of-an-iphone-app-w ith-flash-and-without-a-mac-for-all-windows-lovers/ although some of the file names are as of now inaccurate.

     

    We also got the "itunes sync 'AppName' failed to install" msg.

    It turns out that the Bundle Identifier (App ID Suffix) was incorrect from the application.xml file we used in our FlashDevelop project.

    We were missing the 'air' at the start of the ID.

    We had at our App ID Suffix written only se.domainname.appname and once we changed the App ID Suffix to match the ID tag in the xml it worked, ie we changed it to air.se.domainname.AppName (and at the same time used the correct camelcasing).

     

    With a new profile it worked like a charm after that  :-)

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 10, 2012 6:31 AM   in reply to swfisgood

    Another thing to look out for...

     

    Simply double click your provisioning file to see if it expired

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 24, 2012 7:46 AM   in reply to swfisgood

    I want to add my adventure with this message in case someone had the same problems. I had a problem with testing in-app purchases on an iphone 4. The problem was that the device was jailbroken. I updated to iOS

    5.x. After the update, when I tried to install the application, I got this annoying message, but only when I tried to compile with adt.

     

    When I was compiling from inside the flash builder everything seemed to work fine, but I could not test extensions. The problem was that when I was opening the myapp-app.xml from inside flash builder everything seemed ok and the app <id> was in the form of com.mycompany.myapp.

     

    But when I opened the myapp-app.xml with a text editor, the app <id> was in the form of com.mycompany.myapp.debug.

     

    This debug thing messed everything up. As soon as I removed manually the .debug surfix everything worked ok.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points