I have tried to upload app using Application Loader on Mac.
An upload is succeed however there is not any app in iTunes Connect in my app.
Version and SkuID and AppleID is match between app information in iTunes Connect and the app which is uploaded using Application Loader.
so causing of that, I cannot complete 'submit for review'.
Could you help me please?
Thank you for any further help.
succeed upload app
there is not appearance
Binary on iTunes connect is corrupted. To resolve this, check your binary is compatible with Ios 10.
Please use this link for permission in plist file then try to upload new build with new build version.
iOS 10 - Changes in asking permissions of Camera, microphone and Photo Library causing application to crash
https://i.stack.imgur.com/aY8RG.png
If it's not resolved , please contact iTunes connect support to find out the exact reason. They will reply on mailbox with exact reason of binary corruption. Then needful actions to resolve issue.
https://www.apple.com/itunes/go/itunesconnect/contactus
The problem was to use XCode 5.1.
When I use XCode 6.2, everything went thought well.
Use Application Loader with XCode after 6.
Thank you for everyone.
Related
When trying to upload an App to iTunes connect in Xcode 8.3.3, I get the error:
iTunes Connect access for "Team-Name" is required. Add an account in the Accounts preference plane.
The account already exists and (in some cases) has been working without incident previously.
How do I get around this issue with Xcode so that I can upload my app to the AppStore?
Had the same problem,
First had to export the .ipa to disk using XCode and then upload to the AppStore with Application Loader tool.
It worked.
I suspect that Apple has broken something with the IOS 11, etc upgrades going on. It was all working fine over the last few months, including yesterday, and suddenly today its broken.
As a temporary solution, I had to use export to local disk (from Archive), then select: XCode/Open Developer Tool/Application Loader.
Had the same stupid problem.
Ultimately exported the .ipa to disk (via Xcode itself) and used altool command line tool to upload the ipa. It worked!!
altool --upload-app -f YourIpa.ipa -u <username>
Apple should really spend some $$$ on improving Xcode and the overall Developer experience. Its painful.
I again went back to Xcode to try and upload but met with the same error, so command line was indeed helpful.
A restart to Xcode did the job for me
I just spoke with an Apple rep, and he said I had to update to Xcode 9 GM and rebuild. After doing that, I was able to upload builds again.
On Xcode 9.3.3, a simple restart of Xcode fixed the issue for me.
This goes along with the other answers, eventually I had to export it and deliver the ipa with Application Loader.
However, Application Loader didn't initially work for me. I had to go into my apple id account (appleid.apple.com) and add an application specific password. Then I signed out of Application Loader and signed back in with the application specific password.
As far as I know, xCode doesn't let you sign in with an application specific password. My guess is that Apple broke authentication via regular passwords on their backend, but didn't break application specific ones.
It works for me to follow the steps:
Archive the app with Xcode 8.3.3.
Upload to iTunes Connect with Xcode 9 GM.
I started to panic this morning too, but then I remembered something like this happens every time a new iOS is released. Use Application Loader. Don't start changing certs/provisioning profiles. I'm sure Apple will fix soon. Plus Application Loader is super-easy to use. Good luck!
When nothing works. Just restart your computer and try again! Nonsense but works like magic.
Edit: This worked for me in Xcode 9 GM. I don't know if it will be an issue in the final version
What worked for me is that I changed my regular AppleID email, with the equivalent #icloud.com alias.
For example, I didn't use myemail#gmail.com, I used myemail#icloud.com and it worked.
(Which I really don't prefer, I prefer using my personal email, but if it works, it works)
Same answer here: https://stackoverflow.com/a/46225187/4772647
I did as some of you suggested, I used the Export function in Archive/Organizer to export an .ipa, then go to the Xcode application, use the Show Contents, then nav to "Application" and "Application Loader" and uploaded my app using Loader and that all worked perfectly!
This happened to me when my app was rejected when uploading on AppStore (not sure if this could be connected).
I tried to remove and readd the Developer's account in XCode but that didn't help.
Then it started working after I replied to the Binary Rejected message on App Store Connect and restarted XCode.
Not sure if that could be connected but it started working again instantly after those steps.
In My case none of the above solutions worked,
I have an access for both Developer account and iTunes Connect account, but I faced the same Issue.
The only option worked for me is updating my MAC OS before it was 10.13.4, after update to 10.13.6 the problem was resolved. Hope this will help to someone.
I have been trying to submit a Swift 3 app to Apple from Xcode 8.2 , App passes through all phases but gets stuck at authentication forever and then ends with an error. But then I export app for Appstore submission and then upload the same using Application Loader, tried with two different accounts but no avail. Have referred to this thread as well This action could not be completed. Try Again (-22421)
Most upvoted answer says apple servers may be misbehaving but I wonder how many days ? Is this something specific to Swift app ? I havent tried submitting any ObjC app recently so not sure, can anyone provide a solution ?
I stopped using Xcode uploader after 2 hours of failed uploading attempts. Then I took Application Loader instead and it told me the exact reason of fails. In my case it was too fat watch extension.
Hope this will help.
It's ongoing issue with Apple App uploader server, since couple of days, so you don't have a way, rather than waiting.
You can try following solutions:
Use Application Loader to upload your app, as Xcode organizer can't upload file (rejects IPA) sometimes, without genuine reason and it's frequently occurring issue, with Xcode Organizer, that apple could not resolve permanently.
Solution for error code: 22421
Apple app upload server is not working properly (not in
connection or lost connection during file upload). Just wait and try
again later (may be after a day).
Fluctuation in your network
connection, during file upload.
You may not have added privacy
statements in your info.plist file.
Cocoa Keys: Here, is list of keys that you should consider to add in your info.plist file, if you have used that service in your application.
Nowadays, you may also face, this error code: 90186 (with app loader)
Outdated application loader can be reason of this error. Use latest Xcode tool and use application loader from Xcode Tool.
Incorrect/invalid provisioning profile, associated with your build. Ensure, your have used correct provisioning profile (A provisioning
profile with Distribution/Production mode is require. A Development mode provisioning profile won't allow your to upload app on store.)
You can find latest Application Loader Tool from latest Xcode Tool: Xcode ▶ Open Developer Tool ▶ Application Loader
An internal user who could install and test a couple of early versions of my app, can't install the new version on her device. I didn't change certificates/profiles in the new version. This is her experience with the new version:
The download has been unsuccessful, so I cannot try the current version of the app. It shows the update in Test Flight (version 1.3.2 (6)), and shows it downloading, but then I get an error message that says "Unable to Download App: myApp".
What can be the cause of this problem?
This kind of problem occurs because of the size of your IPA file. I faced the same issue.
If it is above 50mb then try to download it through your WI-fi not from your mobile connection.
For best practices, we should always download an IPA file through wifi to avoid this kind of issues.
It helped me.
Hope it works for someone else also.
In my case was because the user for some reason was unchecked in iTunes Connect.
I checked the user and I sent the invitation again and the user could already download the app
When I try to upload my app to iTC, after validate my app, I begin to submit it .
But there is an Error that said "iTunes Store operation failed
Error Description not available"
When I upload with Application Loader 3.0, same error happened.
I had this error once, too. Then I realized the provisioning profile (Project Targets -> Code Signing) was set to 'Ad-Hoc' profile instead of 'Production' profile. Setting it back to 'Production' did the trick for me.
I've got the Answer,
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 5.1.1 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1 or here
The "Error description not available" sub-error message recently became "You are not authorized to use this service".
Removing the Apple ID from XCode preferences and re-adding it fixed the problem.
I'm a Chinese user and meet the same issue, I tried all these and fail:
Regenerate provisioning profile manually or via Xcode.
Use Application Loader (I didn't use 2.9.1 because I think it's a workaround).
Make sure your developer account are the same as iTunes Connect account.
Make sure bundle ID, version and build string in iTunes Connect and Xcode and the same.
Finally I googled and someone said it depends on network, so I opened VPN, and it success! I guess China's special firewall block something?
If you're in China and you've tried all the steps above, you can try to connect a VPN and upload your app. Wish it helps.
As the error says, There is problem in uploading to iTunes Store and not in code signing. Code signing step is prior to uploading to iTunes Store. Once the ipa is created successfully it should be uploaded to iTunes Store.
I faced the problem and without changing anything It successfully uploaded after some time. I guess if we are doing some operation on iTunes Connect, in my case I was removing the build which was set for TestFlight beta testing. After I perform some changes there the issue occurred.
Not the definite solution.
I had this error, and I found that it was because of the version number in my app. It had too many revision levels. You're allowed a maximum of 2. For example, 1.2.3 will pass validation, but 1.2.3.4 will generate the above error in Xcode 6.
I was getting the same error and I tried for like 15-20 times but was out of luck. Then suddenly it stuck with me what if the network is causing this. Since I was on WiFi, I sat next to the router and it worked in the first go itself. Since there is no proper message by the Apple I tried even this and it worked.
Note: If the size of the binary is quiet large then probably good internet connection is required too.
If you are in china use vpn. I fixed by use a vpn! The gfw block the upload api. you can check this.
This is also workaround but you could upload app with Xcode 5.1.1, if you still have one. Generated with Xcode 6.1 *.xcarchive files are available from older Xcode so there is no need to generate *.ipa file.
Just a tip:
Before you start to change and installing things, try to:
set the Provision profile to another one
update your Provision profiles in your account
close Xcode
open Xcode
set the Provision profile to the right one
Archive again
it worked for me!
In my case i user a wrong account with wrong password !
when i relogin, i fixed the problem, holp it will help you!
I have got this error when I tried to validate a build.
It seems just a few minutes ago I could at least validate and got a different error (with version number, I must increase it to 3.4.1 since 3.4.0 is already approved).
But it may be because I had a Pending Developer Release (v 3.4.0) . May be I have to release that version or cancel the binary. Otherwise I cannot validate the current archive.
I shall come back if that is the reason.
In my case what helped was... to wait. I had just deleted a version of the app and while itunes-connect appeared as I could upload another versione it takes some times to the servers to actually acknolegde this.
Waited until I got an email saying "App changed status to Ready for upload"
This always works for me:
Download the correct profile and certificate from member center;
Quit XCode (Not just close the project);
Try archive and validate again.
I usually get over this with a simple workaround.I get this error when I try to upload archive from Xcode 7.So I archive my project with Xcode 7 but I handle upload process from Organizer of Xcode 6.3.Xcode keep organizer content same across different versions of Xcode.
In some cases it might be a notwork/firewall issue. Make sure your the needed ports are open.
Also iTunes Connect must be working. Currently it is showing "iTunes Connect is unavailable until December 29"....
Here is a blog post about it.
On week were no one will be able to update apps. Greate...
I am trying to submit an app to the apple store via Xcode 4's in-built application loader. I created an archive, then went to itunes connect and made sure the app status is ready to upload. Then when I come to xcode and do 'Validate' or 'Submit', I just get the following message:
An error occurred talking to the iTunes Store
No details are given. Any ideas?
Update: I used the classic Application loader and submitted my app. No idea what the real issue was.
My mbp now run Xcode4.2(4D199) on Lion, I installed the latest java for Lion. And finally I sovled this issue.
Many guys said, he can used the old Application Loader app to upload the apps. so I guess the problem is the latest Application Loader app(2.4.1 (190)), and the fact told me I am right
Okie, in short words:
Here is the solution:
I hope you guys do not delete the old Xcode(4.1). We Should pick up the old version Application Loader app.
cd /Contents/Resources/Packages
cp ApplicationLoader.pkg ~/Desktop/
Now, you get the ApplicationLoader package.
Install the old one.
Tips: you can remove the latest Application Loader app in path: /Developer/Applications/Utilities/ or just remane it.
That's All.
Hope this way can help you and enjoy the new Xcode4.2. Also hope apple developer can saw this problem and test the latest Application Loader app more.
If your target has any spaces or special characters, remove them as they can sometimes cause this error.
It sounds like a connectivity or temporary network issue. I would check your network connection and try a bit later.