Related
I have build the my app which was developed for 5.1 from xcode5 with the deployment target as 5.1 as i want my application to support ios 5 to ios 7.
When i add the application to the enterprise link and when the application is installed in iOS 7 i see the application is being installed twice out of the two apps, one works fine but the other still says installing , I even cant delete the app which says installing . But if try to download the app from link again n while the installation process i was able to delete the unsuccessfully installed application.
Please suggest me how to resolve this issue of shadow app.
Should i change the build settings ? Or is it because of building the old app for ios7 but using deployment target as 5.1 !! I need to solve this problem as soon as possible.
I will be grateful if anyone helps me out.
A couple things that I have discovered with this.
First of all it seems to be less of an issue with iOS 7.1.
Secondly, this can be prevented by making sure that the meta data in your manifest file is correct. Make sure that you have the correct appID (com.yourCompany.yourApp) and it is nice to have an icon included too. See here for what that looks like: https://stackoverflow.com/questions/13236395/ios-over-the-air-installation-black-download-icon-on-retina-ipad
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
Improve this question
I was trying to install my iphone application from testflight.
It installs perfectly on few devices but in some after installing about 80 percent it gives an error Unable to download application, <my app> could not be installed at this time
I am able to find out the reason for, why is it so?
Here's a screenshot:
clear your cache and cookies in Safari, make sure your device is in provisioning profile and provisioning profile is installed on the device.
If everything mentioned above didn't help, try to create a new build with higher build number and try to distribute your app again
Most common issues that cause this are (from testflight's website):
Device storage is full
The provisioning profile is a developer provisioning profile
The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it.
The device was restored from a backup and is causing a conflict for over-the-air distribution
There was a network timeout
Architecture settings of the build and the device are incompatible ( can sometimes happen -when "Build Active Architecture Only" is on when building).
Not Using Mobile Safari.
for me it turned out that my client's ipad was running iOS 4.2.2 and my project supports 5.0+.
Recently default Xcode project settings set ONLY_ACTIVE_ARCH (Build Active Architecture Only) to yes for Debug configuration.
So your build can not be installed on different hardware than the one you use for development.
Change this setting and installation should go fine.
As for Xcode 5.1, the problem was in arm64 architecture in VALID_ARCHS. Building the release configuration for 5.0 device locally gives the following error:
Xcode cannot install or launch applications supporting the 64-bit architecture on devices running iOS versions prior to 6.0. This configuration is supported for distribution through the iOS App Store, but cannot be used during development with Xcode. To continue, edit the Run scheme action and select a build configuration that does not include the 64-bit architecture.
Removing arm64 from VALID_ARCHS solves the issue. In my case I had to create a separate branch for testing on iOS 5 devices.
You can try to publish the application by changing the version of the build.
I was also having the same problem and tried the same by just changing tIt may help you too.
For me Setting Build Active Architecture to NO... works and installed successfully
Watch the console through the Xcode Organiser for the device that is failing to install.
You'll get a helpful message from the system telling you what is wrong. There are lots of potential failure reasons, so unless you check the message, you're just guessing...
Here is what worked for me:
Clear the Cache and Cookies (Settings > Safari).
Remove existing profile (if any) linked to "Test Flight App" (Settings > General > Profiles).
Open Safari and go to https://testflightapp.com/. Login and follow the steps to start over.
P.S. I used to have a Test Flight App, but it looks like it crashed and the icon turned to be all white. Restarting my iPhone made it reappear correctly.
I was also having this problem, with an Ad-Hoc iPad application, when trying
to install it on a iOS 6 device.
What fixed it for me was to click on the project in XCode, and change the
"iOS Deployment Target" setting from 5.1 to 6.0.
And there was silly me thinking that iOS 5.1 apps would run on a iOS 6.0 device.
I just saw this as a result of a network error / time-out on a flaky network. I could see the progress bar increasing after I got the bright idea of just retrying. Also saw HTTP Range requests on the download server with ever increasing offsets of a few megabytes (the entire app was about 44MB).
I had this problem but I fixed this by making sure my Code Signing Identity is the SAME as the one I used in test flight.
After that, everything works fine
This can also happen if you disable cellular data for "App Store" (for example, while on vacation) and forget to turn it back on. The solution here is to simply re-enable it in Settings -> Cellular.
in my case app want to use iCloud services, but in distr. provision profile wasn't set iCloud enabled. turn it on and refresh profile.
I have had the same issue after fiddling around with certificates (argh).
The problem became apparent as I followed the comment of #Duraiamuthan.H, I installed on a device. The device reported 0xe8008016 (Entitlements) see SO here
The initial reason was, that the testflight target used the App store distribution certificate, not the Team certificate. I fixed that and the application was installing on the device over Xcode and then it also worked with testflight.
I had similar issue. However, I was able to fix it when I updated my iPad timings to that of current. I just checked the device log and found that the time in the log was shown 2 years before.
Hope updating the device timing to the current time will fix the issue.
Missing icon could be a problem. My manifest file points to a non-existing image and it fails the installation process. Placing an icon at the corresponding path solved the issue for me.
I ended up creating new Provisioning profiles, not sure if it was because of:
"The ad hoc distribution provisioning profile is corrupted and the device is having an issue with it."
I had the same problem as #mohitum007. In my case the developer of this App included an expiry date in it.
As workaround I set the date backwards to a past date (e.g. last month). Then I could install it and use it.
Also when I set the date back to normal, the already installed App didn't start up anymore. I contacted the company of this App to send me an updated version.
Sidenote: I found out that users from other Apps had the same problem but reversed: it won't install or start before a certain date.
For me, just uninstall the Testflight and restart my iphone. After that, install TestFlight, it works fine !
Check if the deployment target in the General section of the project settings, is greater than that of your device's iOS version.
If yes then you need to update the version of your device to at least the deployment target version. in order for you to be able to install the application on your device.
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.
I'm working on an iPhone project in which the developer that created it has left the company. The Boss asked me to ensure it compiles on the 3.1 iPhone SDK.
After installing, it built and ran fine just once on the device.
After that, it still builds okay, but if I try to run it on the device, it halts saying
Error from Debugger: Error launching remote program: Security policy Error
It won't play in the simulator either, except this time it just says "Debugging Terminated"
Does anybody have any ideas about what might be causing this?
The problem ended up being that there was a provisioning profile (from a completely different project) that had expired. I don't know why having this unrelated profile expire would cause this problem.
Deleting the expired profile from the iPhone fixed the problem.
I have written down a tutorial to solve this:
http://www.drooljunkie.com/code-uncode/beginning-iphone-app-dev-issues-part-2-running-app-on-the-device-issues/
in my case I removed those with the same name ...