I'm experiencing a weird behaviour when updating Xcode from AppStore.
Screenshot:
Xcode 13.0 stuck while installing
I've tried:
Deleting Xcode then reinstall.
Free up storage space on Mac.
Connect to another WIFI.
Disabled VPN.
but no luck
Xcode 13 does take a long time to finish update and install (took me a couple of hours, and it did at times seemed like it stopped installing and was stuck, but it does finish installing eventually - so maybe just be prepared that it might take up to 4-5 hours.
You mention downloading from the App Store, so not sure if you are aware - but you can download it also from the Apple Website Developer Resources: https://developer.apple.com/xcode/resources/ (some people found it was easier or took less time)
There is also a site specifically for Xcode releases, https://xcodereleases.com
It is Not an Official Apple site, but it All downloads are hosted By Apple (download links on this site take you directly to Apple’s download pages). It’s also very well organized.
It seems that it, on the M1Pro, is using only the high-efficiency cores, and they max out.
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 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.
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 ...