I'm trying to upload my iPhone .ipa file to iTunesconnect. I've done that many times successfully using Application Loader, but lately it takes more and more time.
This night & morning I'm stuck at max 15% being uploaded, then my home network completely or partially crashes, and I have to start from the beginning, usually with resetting router first.
Some potentially useful data:
I'm using Application Loader for updating ipa
Application loader uses port 443 for https
.ipa file is about 50MB big
I've updated java as suggested on one stack overflow thread
Firewall is turned off
I have faces a similar problem some time back with Xcode 6, and it was not due to Application Loader, but either my mac or the network. How I resolved the problem was that I used a friend's Mac on a different network and it uploaded smoothly and without any problems. However while trying to fix my problem I came across multiple solutions that may work for you:
Use the default Xcode Build submission tool (The one that you get after validating your .ipa file and it says submit to the App Store)
Use Application Loader (this only works if you were trying with the Xcode uploader in the first place, however I'm assuming you weren't)
Upload from a different network (This seemed to have helped a lot of people.)
Use a different mac. Sometimes the issue could be with your machine. (You can try restarting it, but using a second mac if available would be much better.)
Use the last stable release of Xcode. When using one of the Beta's, try to use the last official release. (And also make sure you aren't using any pre-release technologies, however this should only stop you at a later stage)
You can try any of the above points, as for me a combination of 3 and 4 worked.
Hope that helps, Julian
Related
In the past 6 months every time I upload a new version/build to the Apple App Store through Xcode / Application Loader, it takes between 20-40 minutes for even the smallest app. The uploader is always stuck at the beginning and when if finishes after a huge amount of time, the progress bar just jumps to the end.
Also, and the most annoying, it totally hogs my internet connection (and anyone who is connected to the network aside from me). It’s not usable at all.. it’s really frustrating to upload a build to the App Store for so much time while it totally kills my internet connection -> it happens on any internet connection I try to upload from: Home, office, friends houses, public networks at the mall / restaurants.
When I upload APKs to the Google Play Store, everything works crazy fast (5-10min tops!) and my internet connection is working fine while doing it.
I also tried opening a bug report ticket to Apple, but because it’s Apple, they didn’t even take the time to answer it for almost a month now.
Does this happen to anyone here? Is there a way around it?
Thank you very much :)
It is apple algorithm to validate first then accept application.
Sometime it uploads in 10-12 minutes sometime takes 30 minutes. It depends on internet speed, server load while uploading...
Developers working outside Apple have to keep patience, No Other way
Best is try to upload with Application loader.
I had the same issue and it was completely fixed upon updating itmstransporter.
cd ~
mv .itmstransporter/ .old_itmstransporter/
"/Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/itms/bin/iTMSTransporter"
Please refer to https://forums.developer.apple.com/thread/76803 (look at KumobiusIvan's answer)
First Export the ipa with export functionality of xcode and the upload it with Application loader
You can use this tool provided by xcode it self,
I think sometime the internet connection works well, few ports in your connection internet setting needs to be open.
This might because of the Firewall issue.
We had similar kinds of issue in our organisation but then the link below was helpful for a work around.
itunesconnect using application loader behind a firewall
I have the same problem. fastlane deliver worked for me. Still very slow, but at least it works and does not hog internet.
Here the docs
I have also faced this issue while uploading build through Xcode. There was no indication or progress update while uploading build. So I tried uploading build through Application Loader.
While uploading build to App Store apple performed few checks like
1. It first checks the valid profile for build on iTunes Connect. If there is any valid profile then we can upload build.
2. First thing happens while uploading build is verification of assets and also build validation by iTunes; this is the stage which consumes maximum time of build upload process.
(In my case it took 20 minutes avg. while doing it through Application Loader)
3. Once verification and validation succeed build uploading starts. We can see the upload progress in Application Loader.
As suggested in this SO answer use the Application Loader and uncheck the Aspera and Firmante options in preferences/advanced.
Probably is just enough deactivating the Firmante option.
Also check that you have enough ram for the app delivery. I recommend you to shut down Xcode and any other RAM intensive application.
My situation is very similar to the OP.
None of the above suggestions work for me. Likely the real cause is physical and related how Application Loader is using the internet. I have ADSL2 connection with a Netgear modem/router assigning each device at home a fixed IP address according to the mac address of the network interface of each device. I had noticed that when Application Loader is uploading, my Windows PC could not connect to the internet. However, if in Mac mini I use Safari doing various things like watching video, my Windows PC can access internet.
Even stranger, when Application Loader is uploading, the modem/router could easily lost connection to the internet, as I could see from the LED lights of the modem. The connection is lost randomly at any progress of uploading the 20 MB file.
So I had turned off Windows PCs, iPads, iPhones and Android device at home, so Mac mini is the only device using the Internet, the Application Loading has finally been able to upload the app successfully in one go.
My guess is, my home phone line has some noise, and Application Loader is using the internet aggressively particularly the up link, so stressing out the modem, then causing other devices like my Windows PC lost connection, not even able to resolve host. When Safari is uploading video to App Store, no problem.
So my working solution is to make Mac be the only device using the Internet, given that the internet connection is already in poor condition with noise, near the edge of losing connection.
you need to use Transporter app
you can download it from here https://developer.apple.com/news/?id=10152019a
Having perused many other questions concerning unusual app crashes without any success at solving my problem, I have decided to post this question.
I have an app that crashes at random. Some users (in test) never have crashes, others have an occasional crash. This app is installed via XCode on testers phones, straight from the development machine. The app never crashes when in use, only upon startup a day or two after installation and use.
The app is instrumented with Crashlytics, and no crashes are detected, nor are Out Of Memory warnings. No crash logs are left on the phone after this behavior.
Crashlytics works. I injected test crashes and they were properly detected.
Once the app crashes, it will not restart. The splash screens appears for an instant and then the app closes.
The app uses Core Data and I use ObjectiveRecord https://github.com/supermarin/ObjectiveRecord as the Core Data interface. There are no aborts anywhere in the code (at least none that I added/left in)
The app downloads about 1500 images (photographs) at initialization time, and whenever the photos collection is updated. The filenames are stored in Core Data, not the binary data.
As an experiment, I took the container from the same app on another phone and replaced the container on the defective phone. No difference. Replacing the container on the good phone with the container from the bad phone made no difference either.
If I reinstall the app on the target phone, without deleting the original install, all works as expected. This leads me to believe that I am not suffering from database corruption - obviously, I may be wrong, but if advice can be offered as to how to test this, I will happily accept it.
I am at my wits' end here - any advice as to what the problem might be, or how to diagnose the problem will be gratefully received.
EDIT -- The app is for IOS 9, iphone only.
I shall answer my own question. I have been distributing the app to my 4 testers using a MacBook. I only have one license, and rather than downloading it and moving it between my iMac and MacBook, I was just allowing Xcode to generate a new certificate.
This doesn't work. Ever.
It invalidated all of the copies of the app that I installed.
The moral of the story is: beware of licensing issues - even if you have a license.
and the hint was:
Aug 29 15:48:28 iPhone amfid[170] : /private/var/containers/Bundle/Application/25BE181B-C30F-41FF-87A3-88C8E63BB3B3/TEST.app/TEST not valid: 0xe8008018: The identity used to sign the executable is no longer valid.
Live and learn I guess......
While using Xcode 5.1 to deploy our iOS application I am seeing quickly build and say "Running on iPad Name" but it doesn't launch the application for a little over 7 minutes. When I tap on the status bar at the top for more information it says "SandboxingApplication."
This does not happen on other iPads that we use with the same application.
Any ideas? I've tried all the basics like restarting the device, Xcode, and my computer.
You already said it:
This does not happen on other iPads that we use with the same
application.
That's the point, you'll have to reinstall the iPad. Some time ago I had a iPhone 3GS for testing on which it sometimes also took minutes to launch the app. Xcode behaved like what you described, showing "Running on DeviceName".
But although this iPhone is older it hadn't been always this slow. After I restored it from iTunes it again was pretty much faster.
Finally with the help of #flowmachine1 this is solved! It was fixed by:
Deleting Derived Data
Clean Project
Delete App and Reinstall
Thanks so much!
It could be really any issue, but here are some troubleshooting tips.
Restart Xcode and iPad (You already did it)
Try to create a new Project, and try to run it on the iPad Air (Let me know the comments below what happens)
Reinstall Xcode (Most common fix)
Also report to Apple, if none of those fixes work, https://developer.apple.com/bug-reporting/.
Thank you.
I've nailed down one cause, for my situation at least. The app's sandboxed area is huge (gigabytes) as it contains a large amount of resources (as discussed here). Wiping out these resources prevents the delay in the sandboxing process (with the unfortunate side effect of rendering half of the app unusable).
I can only assume that, as part of attaching the debugger, some processing of each file in the sandbox has to occur every time, and it is this process that is taking the time.
The resources are in the application support directory. If anyone knows of a way to mark or relocate these files to improve the speed of the sandboxing process I'd be very interested to hear (and would award the bounty).
Well, I'm running apps on an iPad Air here and it runs in just a few seconds, using Xcode 5.1 and Xcode 6 (beta 4). So, I'd guess three possibilities here:
Your Mac's HDD is failing, or your app is very large (having GiBs of files OR thousands and thousands of small files). You already said your app has 27MB, so size shouldn't be the issue here. Unless you're talking about a 27MB .ipa file, which is compressed. If your IPA contains 27MB, the app itself can be rather big (not enough for 7 minutes sandboxing time, but affects the sandboxing time.)
You're out of RAM memory on your mac, which causes memory swapping. This can easily lead to 7 minutes build time.
Your USB cable (or port) is damaged. I tried using a damaged cable before, and even with the basic templates that Xcode has I would take several minutes to run it on the device.
I'm trying to submit an iOS PhoneGap app to the app store via Xcode 5.0.2 but I'm encountering problems at the final distribution stage. The app works perfectly on the simulators and devices that I've used and even passes the validation yet when I go to distribute it a number of errors pop up and the project's status is listed as "Failed Validation".
I've had no luck searching for these errors on-line and I don't understand how it passes validation when I click validate but somehow fails it when I go to distribute.
I see other Xcode submission problems are linked to Apple server traffic but I'm not getting any "network connection lost" errors.
I've seen some issues requiring a Java update for Xcode but they seemed to effect Xcode 4 and I'm using Xcode 5.
EDIT:
I forgot to mention that I'm using an iMac on a University network.
After having the same issue I've been able to fix this issue.
To solve this issue you need to:
Go to page 6 "System and Network Requirements" from https://itunesconnect.apple.com/docs/UsingApplicationLoader.pdf
verify that all of the ports and IP addresses are accessible.
After opening all of the ports from the table, I'm now able to upload my apps.
Enjoy!
The problem was that I was using a university network which has a number of restrictions on servers as well as uploading and downloading. The only fix for this problem was to find another Mac to use which wasn't restricted.
A possible solution is to do what #kernix suggests, make sure your bitching corporate firewall isn't trying to mug you off. Are your ports open?
Another solution is to user Application Loader instead.
Open Application Loader, got to preferences (⌘+,) and unselect Signiant and Aspera, but leave DAV selected.
In Xcode i have have created an archive of the app. Verified it no problem. then when i click Distribute i get as far as "Your application is being uploaded" and shows the progress bar.
The bar never moves and after a few minutes my internet breaks. i need to restart my router to get the internet back.
one of the times i received this error "SSL error occured and a secure connection to the server cannot be made"
Anyone ever experienced this or have an idea of whats happening?
Thanks
I also faced this problem: "your application is being uploaded stuck"
My ANSWER IS:
Either just delete your derived data from organizer or Instead of uploading via Xcode, try via it using Application Loader.
I choosed via Appplication Loader and Steps to do that are:
Step1: Make .ipa file via Ad-Hoc Deployment by click Distribution button.
Step2: Find from menu bar of Xcode -> Open Developer Tool -> Application Loader.
Step3: Then upload it that .ipa file in Application Loader.
**
OR ANOTHER SOLUTION
**
For uploading it via XCode:
Step1: Firstly Validate your archive file by clicking on validation button of Organiser.
Step2: Then Upload it to App Store via Oraganiser.This way you can also solve this problem as well
THIS IS MY ANSWER . HAPPY TO HELP :):)
apple uses java ?
my mac does not have problem for internet.any application can download/upload.
except xcode's organizer's distribute or application loader blocks whole internet and modem stops working for a temporal time.
it is obvious not a mac problem. but apple's uploading system strategy seems not good.
they gotto fix this.
I've heard of some users having issues if they're running old versions of Java. If you can't update, or if updating doesn't fix it, you can try:
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5
sudo ln -s CurrentJDK /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0
(other similar workarounds here.)
It could also be an Internet connectivity issue.
Either way, you can also try uploading your app using Application Loader.
I updated my old Java version (from 21 to 51). Is still freezing my Internet.
I validated my archive with Organizer. Is still freezing my Internet.
I tried to upload an IPA with Application Loader. Is still freezing my Internet.
I deleted all my old archives in Organizer. Is still freezing my Internet.
Finally I connected my Mac to Internet through my iPhone's Internet. In resume I connected my Mac to Internet with another provider. This solved my problem
Sounds like my land ADSL provider have some problem with the AppStore.
It will be to do with your firewall on your mac, it may be blocking java all together. Go to settings, security and privacy and then firewall. Once on there go to fire wall options and then there should be an option to allow java to pass through the firewall.
Hope that helps, did with me :)
None of the above suggestions work for me. Likely the real cause is physical and related how Application Loader is using the internet. I have ADSL2 connection with a Netgear modem/router assigning each device at home a fixed IP address according to the mac address of the network interface of each device. I had noticed that when Application Loader is uploading, my Windows PC could not connect to the internet. However, if in Mac mini I use Safari doing various things like watching video, my Windows PC can access internet.
Even stranger, when Application Loader is uploading, the modem/router could easily lost connection to the internet, as I could see from the LED lights of the modem. The connection is lost randomly at any progress of uploading the 20 MB file.
So I had turned off Windows PCs, iPads, iPhones and Android device at home, so Mac mini is the only device using the Internet, the Application Loading has finally been able to upload the app successfully in one go.
My guess is, my home phone line has some noise, and Application Loader is using the internet aggressively particularly the up link, so stressing out the modem, then causing other devices like my Windows PC lost connection, not even able to resolve host. When Safari is uploading video to App Store, no problem.
So my working solution is to make Mac be the only device using the Internet, given that the internet connection is already in poor condition with noise, near the edge of losing connection.
It's very old issue, but in case any of you is still looking for a solution, I stopped using Xcode to upload my apps to the app store. Instead I'm using Transporter (by Apple) and it seems to fix the freezing