I can install an app on my development iPhone compiled with "Debug" configuration using my Ad Hoc provisioning and everything works OK. But when I build it using "Release" configuration, iTunes says: The application XXX was not installed on the iPhone "YYYY" because its resources have been modified.
I've never seen this message before. Does anybody know what it means?
Thanks!
Antonio
We finally got rid of the problem. We were trying to include an image for iTunes after creating the build, but when we used this method (http://iphonedevelopertips.com/xcode/itunes-icon-for-ad-hoc-distributions.html) everything went smoothly.
I'm getting the same issue, and have yet to resolve the problem. I've tried a clean build and specifying iTunesArtwork and neither seems to of alleviated the problem.
The same image and .mobileprovision file works on other computers, just 1 in particular is causing this problem!
We had the same problem during our first Beta. Someone on Windows dug in the xxx.app folder then Explorer created a Thumbs.db file inside. And boum, he got the message "The application XXX was not installed on the iPhone "YYYY" because its resources have been modified." when he tried to install.
He had to remove the app from iTunes, deleted all the Thumbs.db from xxx.app and then it worked.
Incomplete ipa/zip archives (received at the installation end) were the cause for us.
Hello- I'm having he same problem:
The application XXX was not installed on the iPhone "YYYY" because its resources have been modified.
But what I'm trying to find out is which set of files to drag into iTunes for the "application.app" because when extracting the zip file contents sent to us, Windows creates a bunch of misc. files and the .app shows up as a folder instead of an icon. however, there seems to be multiple icons and folders with the same name as the app we're trying to install.
It is working on other machines, but not the one with Windoze XP.
Anyone have this issue?
-J
I had this problem using a run script to cp -R the .app file to the Payload folder, for some reason when the script copied the file it modified it somehow, if I used finder and manually copied the .app file into the payload folder and manually zipped the .ipa file it worked fine. I tested it several times using codesign -v to verify the .app file. it always through the error after a build and the run script. but no error when I would copy the file manually.
The best solution to avoid wierdness like this is to create an IPA file. A good step-by-step guide to creating an IPA target in XCode is here:
http://idotcomllc.wordpress.com/2009/05/26/how-to-build-a-ipa-file-from-xcode/
It starts out with an introductory project so search for "Aggregate" to find the point where it starts telling you how to create a new IPA target for build.
Just in case it helps someone: In my case, I copied the .app to a network drive, then to my Win7 computer before dragging into iTunes - then it did not work. When I zipped the .app first before copying, and then unzipped it on the other end - it worked. Of course, I have no real idea why....
I directly upload the app to a server where the windows can also visit. Then compress it in Windows.
Your debug configuration and your release configuration have some important differences, and release is a lot closer to what ad-hoc should look like. So you first need to duplicate the release configuration and make and call your copy "Ad-Hoc", and make sure you use your ad-hoc provisioning profile with it. Then you need to create a new entitlements file. The new version of Xcode has a cool feature where you can build and archive your app into an ipa file that includes your provisioning profile.
How to do all of this is explained here: http://www.tuaw.com/2010/05/23/devsugar-a-better-way-to-share-ad-hoc-builds/
In those instructions, when it tells you to make the entitlements plist file, it says to uncheck get-task-allow in the plist file. When I created the entitlements file, there wasn't a get-task-allow row at all, so I created one, set the type to boolean, and left it unchecked. It worked great for me.