I just installed itunes 9.2. Then tried doing something I've done thousands of times before: installing an add hoc build. I deleted the old version of the app and dragged the new version onto the app section of itunes. I get a message that the profile with the same name already exists (I select replace). Nothing happens- the app is not installed and does not show up in the app list.
Any ideas? The only difference is iTunes 9.2
https://devforums.apple.com/message/242443#242443
vChav wrote:
Ok, after removing all traces of the
app from iTunes and rebuilding it
worked. Here's exactly what I did:
1) Make a new folder called Payload 2)
Copy the build into Payload 3) Zip
Payload in the Finder 4) Rename the
zipped file MyApp.ipa 5) Drag the .ipa
file into iTunes 6) Sync the device
Thanks everybody for your help!
Ran into this problem as well. The solution was to package the app as an .IPA file using Xcode. The process is detailed here:
A better way to share ad hoc builds
Related
I changed the version number to a higher version in my iPhone app. When I run the application from XCode, it runs successfully. But When I try putting it on my device from iTunes, installation failed.
Any ideas?
I have gotten this error before. It happened because I signed the build and the IPA with different keys by mistake. You need to be sure the one in your build settings matches the one you use to sign the IPA when you make it from the archive. Also of course they both need to be adhoc certificates,
You need to delete the Profile that is present In settings>General>profiles there delete the profile that belongs to your app also delete the app from the iPhone and download a profile form developer.apple yourAccount then drag and drop on the desktop and double click it and then drag and drop both ipa nad that profile in to the iTunes then sync the app will install now
I have created an ad hoc archive and a .ipa file for the application I am trying to distribute. I have also created a distributing provisioning profile with the UDIDs of the devices that I plan on distributing my application to. When I drag the .ipa and .mobileprovision files into iTunes and try to sync the application to the device, an error message on the phone pops up reading "'myapp' failed to install". By the way, I have a standard iOS developer's license ($99 per year) and am using Xcode version 4.2.1. I am pretty new to the developer program, so please try to keep your answers as simple as possible. Let me know if you need any extra information. Thank you!
I had the exact same issue. My issue was simple to fix. Check your Code Signing Identities for Project & Target in your project Build Settings. Mine were pointing to my Development Profile.
The Code Signing Identities need to point to the Ad hoc Distribution Profile that you created.
Make this change and then recreate the Archive and .ipa file. I then deleted the old App in iTunes, and then dragged the .ipa file onto the iTunes icon (Windows). Then I was able to use iTunes to install the App successfully.
My problem seemed to be Xcode. I had multiple copies of the Ad_Hoc profile with different expirations (all valid) and a few with different names from the days. I deleted them all and the app still failed to install, but I noticed all the Ad_Hoc profiles had been resurrected by iTunes. Tried it several times and including deleting them from the Organizer, but they always resurrected (reappeared installed on the device). Finally I drug out a copy of the supposedly extinct iPhone Configuration utility and used it to delete the app and all Ad_Hoc profiles. Then tried to install just the profile. That got it down to 2. Finally got all deleted and got iTunes to install the right profile. Still took 2 more attempts for iTunes to finally install my archive file!
Check this .
Don't need to drag both .ipa and Provisioning Profile.
Just Drag the .IPA File Follow Further steps as you.
Set install owner param in Xcode project / Deployment to the name you specified in apple dev license. I set both install owner and alternative install owner and Install Group and Alternative Install Group to my name which the 100% exactly as in my apple development license.
And the error was gone.
I was having a similar issue where my project was stored on a secondary NTFS drive. After moving the project over to my desktop [aka MacOS Extended (Journaled) drive], I was able to load the ipa file via itunes.
Another point: If the store version of the app installed on your device (or a version deployed another provision), you have to remove it from your device before installing the ad-hoc version.
I solved the issue by not trying to sync with iTunes but instead to sync it within Xcode (from the window->devices menu)
I developed an app and created a .Ipa file and sync it with my iPad1 but the problem is, I am trying to sync the same app in to my other iPad2 using iTunes.
But it is not syncing and showing an error that the App can't be installed and installation failed!!!.
There are several reasons for failed to instal in device.
1.check your provisioning profile contains device UDID of ipad2 added or not.
2.check your ipa file created properly or not.if you feel you created properly then delete the app from your first device which is having same app and instal the ipa again and check once.Then you come to know your ipa creation is correct.
3.one more reason might have take place is ipa may break accidentally.
you can check these steps:-
Make sure that your iPad2 device ID is added to your provision profile you have created in developer portal.
Make sure that your bundle id in your plist is match with the your provisioning profile bundle ID you have choose to build your project.
Second thing you can check if the provision profile is installed on your device on not.
Thanks,
Sandeep
This is a free program to check an IPA file for errors, there's over 20 reasons why an IPA file will fail to install, many strange combinations in mobileprovisioning and info.plist files.
CheckIPA
I have an old version of Xcode so have been unable to create an .ipa file. I also only have leopard installed as the company I work for does not wish to purchase an upgrade so close to a new version being released.
The issue I am having is that when I drag the .mobileprovision file into iTunes that seems to be ok and it does ask if I wish to replace it. When I drag the .app file into iTunes it states 'An provisioning profile named "embedded.mobileprovision" already exists on this computer. Do you wish to replace it?'. If I click Yes then nothing happens.
I had this working on an old iTunes version this morning then updated as a client was having issues importing the .app file. Are all ad hoc distributions done with .ipa files now?
Basic steps I have been following:
2) Unzip the contents of “Sample.zip”
3) On Mac you will have two files, on PC you will have one file and one folder. These will be called “Sample.app” and “XXXX.mobileprovision”. The XXXX refers to whatever name the developer chose for their Adhoc profile (I use Andrews_Adhoc_DP).
4) Open iTunes.
5) Select both “Sample.app” and XXXX.mobileprovision and drag them to the Library panel
6) In your Applications pane you should now see the application which can be synced with your phone.
tldr; Can ad hoc installations still be done with a .mobileprovision file and a .app folder?
Many thanks!
Note to self and anyone who has the same issue:
In the info.plist file "Application requires iPhone environment" should be set to true. (got unticked for some reason)
I have a script working well for creating ad hoc iPhone builds. I can drop the app and mobileprovision file on iTunes (Mac version), and it installs to the device without a problem. But if I generate a new build and drop the files on iTunes a second time, I always get the dreaded "could not be verified" error on sync.
The only thing that fixes the problem is to delete the app and profile from the desktop and device, sync, and then drop the new copy and sync again. I've tried every variation of deleting the profile or app on only the device or desktop, and nothing other than cleaning out both will fix it.
Does anyone know if this a bug in the installation process for ad hoc apps, or am I missing something?
Are you changing your version for each build?
I don't remember getting an error message, but I found that if I did not change the version information each time, I could not drag and drop to install the new version. I would need to delete the app first.
Not sure if this will help, but it is the only thing I can think of so far.