I have created the .ipa file of the application. I have installed it the device via iTunes. It is getting installed on the device but when I launch the application it shows the message "Could not launch application". I have added the deviceId to provisioning profile. Please give me some suggestion on this.
This happens to me some times but it just couldn't launch the app when I get onto my device and scroll over to the screen where the app would be it is there and if I manually launch it on my own it still works... I don't know what causes it, I wish I could help.
Delete your same previous application from iPAD, Now delete all profile and install fresh copy of your application. i hope it seems working....
Same problem i got while creating iPA file. I have solved issue in this way.
First of all check you have previous build in your device. Then you need to relaunch your xcode, build and clean your project using CMD+SHIFT+K then create iPA file and try to install in device. Make sure that you have deleted all previous instances of application and if possible then restart your device. One more thing check same provisioning profile is available in your xcode through Organizer.
This works fine for me.
I'm developing my application in xcode 4.5 and i want to create the .ipa file to transfer the project in to client's device. But unfortunately I can't install it in device. Giving a pop up says "Cannot install".
i have created the ipa and installed it from xcode 4.0.2. So i know the process. I thinks i have given correct provisionning profile too. Is there any reason or anyone can give me a tutorial on this in xcode 4.5?
Did you build the app with an ad-hoc distribution profile that includes the client's device UDID?
Alteratively, use Testflight which works extremely well for this sort of thing.
for replies. i found the solution in entitlements.plist file thr is a property called
get-task-allow. i had to set it to NO.
Tht wat happed with xcode 4.5.
Thank you
Assuming the ipa is correct, is the client's device running an OS supported by the ipa (check deployment target of your project)?
What do you see in the Xcode Organizer console for the device as you perform the install? There is likely an error message in the console that will give you a clue.
Are there any unsafe characters in the .ipa filename? I had a case once where iTunes was installing the app and changing the .ipa filename to be the app name. Well, the app name had a '/' in it, and that doesn't work so well in filenames. The console showed me the error as it occurred.
If you aren't installing with the device connected to Xcode, you can use the iPhone Configuration Utility to watch/record the console on a remote machine.
I just switched from Xcode 3 to 4. When I attempt to upload an app that I have archived to the organizer, I receive this error:
The archive is invalid.
/var/folders/.../app.ipa does not
exist.
This happens after I log in to itunes connect, select the application to update and select next. I am not sure where to begin trying to figure out what is causing this error. Please let me know if I am leaving out anything that would be useful for diagnosing. Thanks
I just faced this problem myself, and I seem to have found a solution to it.
Even though the correct provisioning profile seems to be selected, it might not be.
Try to manually navigate the list of possible provisioning profiles and select the correct one. Do not leave the setting on automatic selection.
In the "Identity:"-list, make sure it does not say "Currently matches...". Manually select the correct one yourself.
That should fix the problem and you should be able to upload to the AppStore.
Okay, so when you install the Xcode 4 package, make sure you have the "Unix Tools" option selected. This was the problem in my case.
If you are running an Xcode beta version (Apple calls it a "developer preview") you will get this error because you're not allowed to submit apps from a beta version. This restriction is not mentioned in the Read Me file or on the Xcode download page. To submit an app, you will need to uninstall Developer Tools, then reinstall the latest non-beta version, then restart your computer.
Here's the command-line command to uninstall:
sudo /Developer/Library/uninstall-devtools --mode=all
Quit Xcode
With a text editor open the file YourProject.xcodeproj/project.pbxproj
Delete all lines containing PROVISIONING_FILE =
Delete all lines containing CODE_SIGN_IDENTITY =
Save & close project.pbxproj
Reopen your project in Xcode
Clean the project
In the Build Settings pane choose the correct code signing identity
Rebuild
I recently switched to a new MacBook Pro and had XCode 4 installed from a Time Machine drive via the Migration Assistant.
Re-installing XCode 4 with the Unix Tools fixed it.
For some reason those files weren't getting copied across with Migration Assistant.
I had the same issue for both TestFlight and App Store. The solution for me was to archive the app, and in the organizer select "Don't sign" when you try to validate/submit or share (in the case of TestFlight).
Hope this helps.
In my case this has nothing to do with Xcode or the unix tools. Indeed I happend to had too many distribution certificates (Why? I don't know). Deleted all of them but one, code sign with this one, re code sign it while validating and submit it with no errors. I hop this help.
A good way to test is to run the build from the command line. Change to your project folder and run 'xcodebuild' and look carefully at the outputs, especially around the 'codesign' command.
I did this and discovered the following:
architecture armv7 object: /Users/chris/Documents/x/x/build/Release-iphoneos/x.app/x malformed object
object file format invalid or unsuitable
So it isn't a solution, but it at least lets you zero in on what the problem is. Anyway, for me, looks like an architecture config error.
Update - to fix this problem, i replaced the copy of codesign_allocate in my /usr/bin folder with the one in /Developer/somewhere and that fixed it.
I tried most of the ideas above, and they did not work for me, likely because I am using he Appcelerator Titanium platform. I did however delete the Build directory and re-built the product and it passed the validation and I was able to upload the binary to the app store.
The same happened to me. My mistake was I had certificates with similar names (like "Provisioning Profile of Giammy", "Profile for Provisioning of Giammy"...).
Running "Archive" from XCode 4.0 and then "Validate..." from the Organizer I faced the "app.ipa does not exist" issue. The problem was that I selected the wrong certificate from those with similar names. The "Archive" phase worked good but the archive did not pass the validation.
Solution: just picked up the correct provisioning profile in the "Archive" phase.
Lesson learned: check twice the provisioning profile name!
Make sure that you are signing with keys for correct product/bundle ID. If I remember correctly, mixing that up could lead in archiving problems.
Also, go to that temp folder and check what IS created. Maybe xCode is creating the IPA under a different name, that could give you a hint.
I solved this same problem by deleting all of the expired signing certificates from my Keychain. Xcode seems to just grab the first one it finds with the given name, regardless of whether it's still valid.
I tried everything including reinstalling xcode4 with unix tools. NOthing works.
I assume I shouldnt have to do this as I'm able to submit other apps without issues.
I'm just having this issue with a partiular project (coming from xcode3).
I even created a project from scratch, imported all the code over and tried again - failed.
so it's not only my project but something in it.
So I've started the process of creating a new project, adding some files, then submitting, then rejecting to figure out what's causing it. This is working so far.
update: ok - it has something to do with using CorePlot and linking it in as a library. and voila - found the answer here.
Can't submit app with CorePlot using Xcode4
Solution: when submitting select "Don't resign"
I was not able to solve this problem by changing or fixing code signing identities (which should resolve this problem in many cases. Nor did simply reinstalling Xcode. These are the top two solutions as I post this answer.
I found success in uninstalling all the developer tools, and reinstalling from scratch.
Here is how I solved it:
Open Keychain and delete all distribution certificates, both from my "login" and from "system".
Download the latest Distribution certificate from the Dev Center.
Double click the certificate to install on Keychain.
On XCode, make sure the certificate name matches on Build Settings.
Build for Archive (a Keychain popup should ask for permission to sign the app).
Archive (again, Keychain confirmation required).
Validate archived app (again, Keychain confirmation will be required).
Submit app (one more time, Keychain confirmation will be required).
If you are building for Archive and you don't see any Keychain confirmation dialog, you can stop at that point because submission is not going to work.
i did have this very same issue using xcode_4.2_and_ios_sdk_5_beta__snow_leopard, my working solution.
Install the previous (non-beta) version of Xcode in a different location and work with that version, and that's it, it worked i was able to upload my app to the AppStore without any inconvenience.
regards,
Jorge.
Never try to submit using apps you built using beta SDKs as your base SDK.
I got rid of this problem by uninstalling all developer tools with the below command
sudo /Developer/Library/uninstall-devtools --mode=all
and then restarted my system and installed that latest non-beta version of XCode and non-beta iOS SDK.
Have you been playing around with the ENTITLEMENTS_REQUIRED attribute at /Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS4.3.sdk/SDKSettings.plist (let say to create jailbroken applications)?
In this case, please reset ENTITLEMENTS_REQUIRED to YES.
for xcode 4 I tried every thing but I can t solve this error until
install xcode 4.2 for snowleopart
if you cant see your app icon in validation page its can be your xcode have error.
download from apple developer page xcode 4.2 and install. its solved.
you dont need to uninstall your xcode 4 just download new xcode 4.2 and install.
I am very fine now
My solution was:
Open the info.plist file in your project and in product name write your products name instead of $[PRODUCT_NAME]
Had this error in Xcode, but had no such error when using the Application Loader. Get to it via Xcode -> Open Developer Tool -> Application Loader. Very frustrating indeed.
We are getting an error when deploying an iPhone application to iOS 4 using the Windows configuration Utility, 3.0. The application loads great using the configuration utility on a mac, fails on windows.
We have confirmed that the provision is copied onto the device, it's just the app.
The error is:
Could not install application on
device. Error: A signed resource has
been added, modified, or deleted.
Several posts talked about special chars used on macs not working on the PC, we have been careful to only use allowed chars in the name of the app.
Any advice on this would be great, and yes, we suggested they buy a ton of macs already. :)
Had the same error. Finally manage to get around by installing my application using the windows version of iTunes . Forget the iphone configuration utility for installing apps. It's too buggy :(
I am getting an error while uploading my app on device. It does installs it but not able to upload it.
Also I want to run the instrument tool on device but when I run it shows nothing.
Anyone facing the same issues.
I had this problem after changing around provisioning profiles and app ID's.
What fixed it for me:
Quit XCode
In Terminal.app, navigate to your project directory and execute rm -rf build/
Restart XCode
I also confirm, that I had that issue on Xcode 3.2.5 and iOS 4.2 GM Seed and after adding new provisioning profile.
You do not have to use terminal, you can select *.app from Products Group in 'Groups & Files' pane in Xcode. Then right-click on it, and select 'Reveal in finder'. Then manually delete the build catalogue. And restart Xcode.
Worked for me.
I was getting this issue on an iPhone running 3.0 software, but it was working fine on phones running 3.1. The app used to work on the 3.0 software until we added users to the provisioning for the app - this is the only thing I can think of that might have caused it.
If you're running 3.0 still, try upgrading to 3.1 and see if that fixes it.
I had the same error message in iOS 4.1 but from a different cause: when trying to link to a universal (ARM & X86) static library that was over 10MB. If I link directly to the ARM version of the static library (for iPhones), then it works fine.
Sometimes manual delete of Build folder of your application fails to solve the problem
"Failed to upload the .app on device"
Try
WIndows->organizer->Provisioning profile(in left pane)->refresh it once....
This has solved my problem!