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.
Related
I am trying to run an app on my physical device, it starts to build onto my device then crashes due to an 'invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.'
I have updated my iPhone and Xcode to the latest release, tried to clean the build and edit run scheme build configuration to 'Release' and tried to set my executable to 'Ask On Launch'. I searched for a Iphone Developer file on keychain and could not seem to find one but i am not sure what i am supposed to do.
Can anyone help?
The problem is that the developer is not trusted on the device. If you manually try to run the apps on the device, you will see an Untrusted Developer message.
To solve this issue on the device, go to Settings > General > Profiles or Settings > General > Device Management, depending on the device type and the iOS version. There, trust the developer and allow the apps to be run.
For newer versions on your iPhone (version 14+)
Settings > General > Device Management (In the VPN section past Date & Time section).
Then trust the device
Adding newer settings
2022 iPhone 15 variation. Load the app --> Next as below.
Settings > General >
VPN & Device Management > Developer App > Trust "Apple Development:....."
Please check the internet connection of the Testing IOS device, Signature verification fails if device isn't connected to Internet.
I had the same issue, I just
Created a new Project with the sample Hello world
Deployed it to the device - it was working
Deployed my desired app again and it started working
I hope it helps.
If nothing works, do this,
Open XCode -> Window -> Devices & Simulators.
Remove your device from that window.
Reconnect the device and you will receive the trust certificate again.
This work after upgrading to iOS 15.
on your iphone,
Settings > General > Profiles or Settings > General > Device Management
Developer app. (Click on) for trust.
In my case simply reconnecting the lightning cable did the job.
If you see this issue happen out of nowhere, one other possible source of the problem is a network outage.
Your device will periodically need to dial out to a service to validate the provisioning profile. I don't have details on how often this needs to happen but I do know this validation action happens during the app's startup. If your device can't connect to the internet or Apple is experiencing an outage, it can interrupt this process and produce this error.
You can check the status of Apple's services here:
https://developer.apple.com/system-status/
Certificates, Identifiers & Profiles is what you want to keep an eye on.
If none of the above works and you've already trusted the developer, try 4G/5G connection instead of wifi.
This problem occurs because the installed app's developer is not trusted by iOS device.
To solve this issue on the device, go to
Settings > General > VPN & Device Management
Here is the screenshot
I am getting this error - http://help.testflightapp.com/customer/portal/articles/829652
I tried this (but did not fix the problem) - http://help.testflightapp.com/customer/portal/articles/867631
I tried installing the adhoc build via iTunes (still no luck) - http://www.youtube.com/watch?v=OF7bstiw_9o
I am using the AdHoc provisioning profile(with my phone listed in it) and distribution certificate. I also went ahead and deleted/created a new adhoc distribution profile, just to see if that fixes the problem.
Also if it counts, I am building for iOS 7.0. I can see the adhoc provisioning profile installed on my iphone via the iPhone Configuration Utility.
Anyone know where I could be going wrong?
One of the potential causes listed in the link you posted is 'Architecture settings of the build and the device are incompatible ( can sometimes happen when "Build Active Architecture Only" is on when building).'
One possible reason for this is that you had the device connected to the computer when you did the build. The build may have been optimised for the architecture of the attached device and the device you are trying to install to may have a different architecture
I'm new to xCode development and struggling my way through the provisioning system trying to run a Hello World app on a real device. I went through al steps and everything seems fine but one thing:
When i click my device (Iphone 3G running IOS 4.2.1) in the xCode organizer the following message is displayed under Software Version: Xcode cannot find the software image to install this version...
Also the provisioning profiles show no status in the organizer (both in the library and on the device). On the provisioning portal they have the status active.
I hope someone can help me, thanks!!
ps. i am working with xcode 4
Update: OK, I've found the solution -> set deployment target to 4.2 in info tab: https://discussions.apple.com/thread/2780316?start=0&tstar
The message "xcode cannot find the software image to install this version" seen in the organiser window... This is just a notification rather than a problematic error.
If you want to eliminate this message anyway, I found I was able to do this by running restore within iTunes. Part of that process involves downloading some stuff, which I presume is the 'software image'.
But, as explained in Technical Q&A QA1569 "This message does not prevent you from using the device for development purposes. The only effect is the inability to reinstall the OS currently on the device using Xcode." ...and that has been my experience. Back in the main Xcode window you're still able to click 'run' and send the app to the device to run.
...and it will run assuming everything else is set-up OK, but there are various other gotchas related to Xcode 4.2 and v4 devices:
As mentioned by Overbeeke you should ensure the 'deployment target'
of your project is set down to the desired version (the minimum
version of the devices you want to support) Additionally I would
point out that the 'SDK version' should normally remain set to the
latest (it's whatever SDK Xcode on your machine is using)
As mentioned by Kenneth Lam, in the new Xcode you need to frig around
with "armv6/armv7" settings if you want to support earlier models of
iPhone. Follow these instructions to add the right "Architecture" armv6 setting. Additionally I would point out (as per this answer further down) that there is a setting called "Required device capabilities" from which you need to remove 'armv7'. This is in your app's plist file.
I'm saying all this like I'm an expert, but I still can't get it to work on a v3.1.3 device :-)
I think Xcode 4 requires that you are running the latest iOS to use that feature, but you don't need it to install apps on a device. I have run my apps on an iPod Touch 1G (which can't be upgraded to iOS 4.3) with the same iOS as you and it worked.
Have you added your device to the provisioning profile?
What I did is opened the organizer, right click on the device on the left pane and select "Add device to provisioning profile" where you will be asked for your Apple ID (within xcode) and it will add the device to your profile without you leaving xcode, much simpler than using the online portal.
Xcode 4.2 only builds armv7 targets by default. (Iphone 3G running IOS 4.2.1 is armv6) Add armv6 build targets by following these excellent instructions from Nick "Warning: iPhone apps should include an armv6 architecture" even with build config set
just an update, to update the iOS deployment target, click your project in the left pane, the one with the blue 'A' icon. click the build settings tab (not info), instead of showing "basic," show "all." iOS deployment target is in the deployment section.
There could be a number of things, but i would make sure that that your deployment taget in build settings is at or below your target . Check the "deployment section" in the build settings of your project. The default sets the deployment to the highest iOS version, if the ios version is below what is set you will not be able to run the app on that device.
I've sent my iphone application to my testers and all but one complain that the get error OxE8003FFE when they sync their devices. They are not able to install and run the application.
I'm using an ad hoc distribution provisioning profile and all of the testers devices are included in the profile.
I'm not sure how to proceed and would really appreciate any help you might be to give.
One more interesting bit of information: The program is a universal iPad/iPhone application. My testers are able to install it on their iPads but not their iPhones.
Did you properly add entitlements.plist, and uncheck the box therein?
I would recommend having one device locally that you deploy to through iTunes (not building through XCode), to test that the IPA file will work for other testers. That may mean buying an iPod touch, even the very oldest one will do (if you are targeting 3.x users).
I'd suggest you to right click your package, find a file embedded provisioning profile and open it with TextEdit. See that the name of the profile you've signed your application is indeed of that of ad-hoc.
After that be sure you sent this file (embedded provisioning profile) along with your ad-hoc build to your testers, because they have to install it on their devices, it's not being done automatically and w/o that profile your ad-hoc build will not sync to the device.
After some back and forth with DTS I managed to fix this issue.
The problem was that I was compiling for armv7 only which caused the installation to fail on armv6 machines.
Another interesting bit, the default universal project template and iphone projects converted to universal will compile for both architectures by default, this didn't happen for me bacause my project was initially an iPad only project which I converted manually (since there are no automatic tools for this) to be iPhone/iPad universal, this is the probable reason for this setting being incorrect in my project.
I'm trying to install Zxing on my iphone from source (I know I can get it at the app store, but I want to modify some things in it).
The problem I'm having is that the app won't stay installed on the phone. It will run without a problem, but no icon will appear after I quit the app. I thought it had to do with my manually editing the codesign information in the project.pbxproj but after the developers changed the codesign identity they had left in the checked in version, the problem still persists.
I tried deploying an app I had developed from scratch and that worked fine.
I'm new to this, so any help would be much appreciated. You can download the zxing code from here:
svn checkout http://zxing.googlecode.com/svn/trunk/ zxing-read-only
Have you downloaded a copy from the App Store? I had one app (built from Xcode) that wasn't staying around after a sync and I found it was because iTunes was looking at my application syncing preferences and it wasn't selected to sync (as I had the Xcode build version on there, I didn't want to sync that version). However, it presumably removes the built app because I said I didn't want to sync any version of it.
Checking the checkbox to sync the app in iTunes kept the Xcode built version on there without installing the App Store version.
Hope this helps.
I think the problem had to do with my iPhone firmware. It might be a bug from Apple as I got an email from truphone saying that users were experiencing similar problems. I re-installed firmware, and could install it fine, and sync other apps. As soon as I did a restore from a previous backup, it broke again... what a pain. Case closed.