Related
I've had an iOS project in fairly stable condition up until Xcode 8's public release. After a bit of confusion with the Migrator, I finally convinced the compiler that I did not want to go Swift 3 yet, and that my code was indeed valid Swift 2.3. Not sure if this at all relates to what the Organizer does in validating my long-awaited archive with some long-overdue fixes for iOS 10, but we'll see...
Anyway, I got Xcode to archive my latest build (which runs fine on my iPhone 5s by the way). I tell Organizer to "Validate..." in preparation for an upload to iTunes Connect. After a good deal of doing its thing, it finally spits this at me:
Been at this for three days now. Application Loader gives me something similar, but not much more helpful:
Following the suggestions in this answer, I find that every single one of my compiled assets read as sRGB, not 16-bit, or P3. Aside: When does an API analysis file get "too large"? I mean, sure I use Apple's APIs a lot, but I can't be alone in that. That's what they're for, right?
I've tried (almost) everything I can think of. I've redone my code signing a dozen different ways, read and recombobulated the build settings wherever I thought could be relevant, and tried every combination of bitcode and symbol inclusion available to me. Just about everything I could come up with short of migrating to Swift 3! Could that really be my solution? It's a rather big jump, and with the time I have, I'd prefer to get this working build out to my users before I'm slammed too hard to shore up the updated codebase.
I can't seem to find anything on "ITunesSoftwareServiceAuthenticationErrorDomain", or this mysterious "error 434". The only reference I've found so far leads to a dead StackOverflow question. Really wish the author hadn't removed it... Wonder if he found his answer?
So my question is as follows: What am I doing wrong to get these errors, and how can I fix them? I'd rather not have to upload without symbols or bitcode, so if that's the workaround, I'd like to know why, so I'm not limiting myself for something dumb.
Cheers!
I had the same problem with Xcode 8.2 while submitting my application:
ITunesSoftwareServiceAuthenticationErrorDomain error 434.
Solution: I switched to different network and it worked for me.
Bump the build number and validate again.
Had the exact same problem. I tried upgrading to Sierra which seemed to update bits of Xcode etc. The new error message was formatted differently, so I could not see the "434"
(With 1 success in 15 attempts (I had to tweak a version number in a string in the app, so didn't choose to upload after that brief moment of joy), i just uploaded the archive anyway, and after 2 hours of processing, it was accepted. I will update when my new app version is live to verify this error can be safely ignored, at least in some cases (e.g. I checked all my graphics' color profiles, etc.).
Do the below steps :-
1. Analyze the project. (From Product Menu)
2. Click on Archive. (From Product Menu)
3. Select the development team for provisioning.
4. From summary window unselect "Include bitcode" and click on Validate button.
Now, It will working fine.
I solved it by uploading my app through Application Loader.
Archive app Export ipa iOS Deployment
Xcode-> open developer tool -> Application loader
I had the same problem while I was trying to submit the app to client's iTunesConnect account. I've signed in with new apple id, downloaded the certificates and provisionin profiles but still got this error:
(ITunesSoftwareServiceAuthenticationErrorDomain error 434.)
How to fix this error?
Try to remove Provisioning Profiles files at ~/Library/MobileDevice/Provisioning Profiles/
Make new Build and Archive the app. Xcode will create new Provisioning Profiles and submit the app to iTunesConnect.
Just to share this.
Quit xcode and re-login as suggested by members does not work for me. I solved it by using "Application Loader"
Steps: 1) change the version and build in your App 2) archive again for new file submission and export file to desktop 3) goto top menu: Open Developer Tool > Application Loader (if you don't have this , search, download and install this plug init) 4) upload the new version archived file. Done
You will find them in iTune Connect. From here process to My Apps > choose the rejected app > change the version and click on the new uploaded archive file, file will be processing..
5) time to resubmit :) cheers
Clicked Valid until it succeeded, 3rd time.
Since there seem to be many solutions to this problem, it may just be an issue not related to anything developers have control over and the "solutions" seem to be "solutions" because after some action was taken, it succeeded. The action I took was the non-action... and it was successful.
Hope this helps, as this is a stressful problem to have when you cannot upload your app and muddling around in Xcode to fix it you might break something else.
I fixed it by upload using Application Loader.
Besides, after upload the app i receive the warning about Privacy - Photo Library Usage Description and Privacy - Camera Usage Description, so that, please make sure you have them in your info
Hope it help!
I had the same problem. In my case it was caused by following. I had a lot of png-files in assets.xcassets and some of them had AdobeRGB Color profile. I changed the profiles to sRGB and xcode validated the archive with no error.
Frankly speaking, when I changed the profiles some other strange errors occured, but they dissapeared by themselves when I tried to re-validate the acrchive several hours later (I did nothing just waited).
If this occurred randomly, try to delete that archive and make sure you have "Generic iOS Device" selected as target when you run Product > Archive again. This solved it for me.
I Got the same issues when i try first time.Next time it Validated successfully. Please check network once before trying second time.
1.Cmd+Shift+K
2.Close Xcode
3.Open Xcode
4.Cmd+B
5.Product->Archive
Just Clear all file in Path ~/Library/MobileDevice/Provisioning Profiles
Go to Xcode Select Provisioning profile again and then it auto-generate again.
So It will be working fine.
In my case it was the following:
my account had been logged out and I had to enter the password again
Xcode v8.0 had to be updated to 9.x to be able to publish to the App Store (as of July 2018)
I fixed this problem by updating Xcode from 8.2 to 9.
Apparently there was a compatibility issue with an SDK used internally. Xcode was not helping with it's error message. I discovered it by using the Application Loader to upload the archive. Application Loader's error message made some sense.
This is quite linked to this question but it doesn't have any solution.
On uploading a build to iTunes Connect, I received the following message:
We have discovered one or more issues with your recent delivery for
"Hurdal IL". Your delivery was successful, but you may wish to correct
the following issues in your next delivery:
Unexpected Machine Code - Your upload contains both bitcode and native
machine code. When you provide bitcode, it's not necessary to include
machine code as well. To reduce the size of your upload, use Xcode 7.3
or later, or any other toolchain that removes machine code.
After you’ve corrected the issues, you can use Xcode or Application
Loader to upload a new binary to iTunes Connect.
What is the resolution?
Will the app approval be affected if this build is uploaded ?
I just talked with the Apple Developer Support, the official one. They don't said it clearly, but yes it's a bug.
So, it's confirmed that there's some malfunctioning in their side.
UPDATE: It won't affect the Apps in Production neither Testing!
I have same issue but in my case I set in Xcode Build Setting Enable Bitcode to NO. After this error I change it to YES and it works
No, its not effect app approval and the binary seems to be accepted by the iTunes store.
I just uploaded a binary recently (like 20m ago). They did sent me a note just like you. After that, I just re-built it again, only update the build version (1943) and upload. Now it seems like there's nothing happened anymore. And the previous build (1942) has completed processing without failure. So I doubt it's a bug from Apple.
Just ignore it. You may want to build another binary to fix the warning tho.
I've the same problem, I send my application to review with that issue.
Result:
My app pass the review and already in publication. No problem... I think it's a issue from iTunes Connect.
The app which I published with this waring was just approved by Apple. So to answer my question, this won't affect the app approval.
Also, I am accepting #Helen Wood's answer as she was right that this is an apple bug.
Just got this as well, it's a bug. I uploaded the near exact same binary as I did a couple of days ago which went through fine (only change was to the version and build number). Developer support confirmed this.
If you do get the e-mail, don't worry about it. Your binary will still process and you'll still be able to submit it to the app store.
After submitting my app through Xcode, I see my app with no icon and it says "Uploaded" in the prerelease tab. What should I do? It's been two hours. I validated and submitted without any issues through Xcode. Here's what I see:
Update:
It's been about another 2 hours and I still see:
Update #2:
It's been another 24 hours and nothing!
Update #3:
I've contacted iTunes Connect Support addressing this issue and they said they would give me a call after they get in touch with the engineers. Here is what they said through email:
I will follow up with you as soon as I have an update. Thank you for
your assistance and continued patience.
Final Update! SOLVED!
After a drastic 5 days of just getting this app to review, they've finally fixed the issue. It seemed to be an issue with the server. The best help I can give to those stuck is to try to send another build or contact iTunes Connect Support(it's faster to call then to email). Also, if you get your app sent to review, don't forget to request an expedited review from Apple, to make the review process faster (not every one is guaranteed). Thanks so much for all of your support!
Wait more. It will be processed eventually.
Apple may have issues with their validation servers or could have a very long pending apps queue. Just be patient.
Edit: (from MGame's experience)
If after a few hours, your build still hasn't started being processed, give a phone call to Apple. It seems that in some rare case your app could get stuck in their servers and they have to manually resolve the issue.
Please check your email inbox.This may be the issue
"Dear developer, We have discovered one or more issues with your recent delivery for "App Name". To process your delivery, the following issues must be corrected: Missing required icon file - The bundle does not contain an app icon for iPad of exactly '76x76' pixels, in .png format for iOS versions >= 7.0. Missing required icon file - The bundle does not contain an app icon for iPad of exactly '167x167' pixels, in .png format for iOS versions supporting iPad Pro. Missing required icon file - The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 7.0. Once these issues have been corrected, you can then redeliver the corrected binary.
I have the same trouble. I tried the following:
Increase the second build number
Resubmit binary
Then my app process was completed immediately.
I have added myself as App Manager and Got email that i need to add NSPhotoLibraryUsageDescription in info.plist. For more Details see this answer.
https://stackoverflow.com/a/39650451/1394622
But as i am writing this answer also working for people. It says just don't put xcode in background and let it run in foreground while you are uploading.
https://stackoverflow.com/a/26655249/1394622
After waiting for a week without seeing builds, I've try Application Loader from Xcode 8.1beta.
Steps:
Archive
Export -> Save for iOS App Store Deployment -> Save a folder with IPA in my desktop
Xcode -> Open developer tools -> Application Loader -> choose IPA file from desktop
Now I can see my builds..
Another simple thing to try is to update the itunes Connect Form of the app version.
In my case, the builds only appeared after I've put something in the first field ("What's new in this release") and saved the changes.
Add missing items in info.plist,such as icon files, privacy usage description, requirements etc. it works for me
Wait for sometime. You can see the build. In my case it happened like that.
I regenerate all of the certificates, update the version number of the application, but the problem persists.
Follow the below steps.
Go to My Apps Page.
Remove the Build. Then Save It.
Re Add your Build. then Save It.
Now try to Submit It must work.
I do not know what the reasons are, how to do?Thanks!
In Prerelease section the status of your build should not be "Processing". Just wait some time (10-20 min) after build upload, and it will be ready to use.
I got this problem in Chrome browser. Switching to Safari worked like a charm for me.
I had the same issue. To solve it, the unique thing I had to do was "Clear History and Website Data..." within Safari (version 8.0.3 in my case).
Please, keep in mind that I speak from my experience and that worked for me. I cannot guarantee this as a general rule to fix the problem. Nevertheless I can assure that I tried several alternatives explained here and the one I just described was the solution for me.
It seems to happen if you are too quick between the build finishing "processing" and it being attached to a version and the version being submitted. I just published two apps in quick succession and the second submission had this problem while the first was fine. The only difference - speed of clicking the submit button.
Logging out and back in made no difference - the "problem" is with the submission.
I removed the just uploaded build from the version and then re-attached it, proceeding as normal to submit the release to Apple with exactly the same build and submission artifacts as before, except this one "saved" and went into the review queue.
I got the strange but working solution.
I had tried submitting the app using Safari browser but it didn't work and showed same error. Submitting the App using Chrome worked for me in the first go...
I'm stuck on this too; and have had to work around several other iTunes Connect bugs just to get to this point. What were Apple thinking by releasing this iTunes Connect version? It's completely ridden with bugs!
Sorry, I've tried everything I can: Filing a support case with Apple appears to be the only 'solution' at this point.
Make sure the Version you have on iTunes Connect and the version you gave in the Info settings in xCode are exactly the same.
I had 1.0.0 in iTunes Connect and 1.0 in xCode and it kept giving me this error message. I changed it to 1.0.0 in xCode and it worked perfectly.
I had the same problem. just sign out and sign in again. it should work.
I had the following issue when submitting a build which was uploaded couple of days ago for test flight testing. Then figured out that the provisioning profile of the application has expired so I renewed the prov profile and downloaded and re-archived the application (by increasing only the build number ) and uploaded and submitted it. And it worked like a charm.
I guess apple need to be specific of these error scenarios
In my case we contacted apple and they said the issue is that it seems that we don’t have a correct certificate generated on developer.apple.com. We use Xcode automatic signing management. I refreshed correct profiles, rebuilt and I could submit successfully.
I had the same problem. Tried from different system and it got saved
I'm trying to upload an iOS app for review using Xcode's Organizer and I've encountered two problems:
Case 1
Binary uploads but when I press Submit for Review iTunes Connect gives the error:
Your app information could not be saved. Try again. If the problem
persists, contact us.
Case 2
After getting the first error message, I tried uploading a new binary, but got the following error message in Organizer:
ERROR ITMS-9000: "Redundant Binary Upload. There already exists a
binary upload with build version '1.1' for train '1.1'"
I tried uploading other binaries changing the version number but still I can't get my app to go in the review state. I also can't see any way to delete old binaries that were uploaded.
Another observation: My app should be around 30MB but when I look at the uploaded binary it is only 1.46MB. I guess there might be something wrong from the binary but I've built it using the same technique several times before and never had any issues.
Any ideas?
For me, I was filling out the form in Safari and getting the error. I logged out, then switched to Chrome and signed in. This fixed the error, and I was able to submit.
Sign out and Sign In again should work as it worked for me!
I solved this by increasing the number in Build (Select the Target, then Xcode -> General -> Build, see picture) by adding .1 so the build was 3.75 -> 3.75.1.
But only for the Build, the Version is still 3.75 and also appears like that in iTunesConnect.
Then the new binary uploaded and I could select it for review. In the picture below you may see the old and the new binary listed in iTunesConnect. Then I finally just had to select the new binary and submit for review.
Open web inspector, you will find that Apple said: We've got a server error ... 500
That's the real reason. :)
Update:
Inspired by #phantom, I try to use dotjs to run a javascript script to auto click submit button per 15 seconds, but still get the 500 error all the time.
#Geaka's answer is working for me. Because my product name is Chinese，I change my product name to english(DO NOT include whitespace! It maybe causes another error on building path error.)
I debug the apple website and find a js script named submit_for_review_cntrl.js which controls the whole submit progress. From line 123 to line 129(formatted by {} button in chrome) that setting the http headers, there is a field named X-Original-Filename, the value is given by $scope.addCcatFileToJson method in line 138, the param of this method is given by ajax callback, i guess there's a bug for encoding the product name field of the back-end code.
WTF Apple!
We just solved our version of the problem (generic error message)...
After hitting submit for review I was trying to upload a file for the ERN since my app uses encryption. It finally worked when I used a zip file that contains an image of the ERN response and a txt file describing what encryption is being used.
The problem unfortunately still occurs. My solution when this happens is removing the binary, clicking on the save button then adding the binary again. Then save and follow the standart procedure. That solves the problem for me without changing the build version or doing anything extra.
Finally find the solution:
Steps:
If your app version and build version is 1.0, keep version 1.0 and change build version as 1.1(bigger than last build version), then upload it.
If your app name is English, choose this build and submit to review, it would be change to review.
If your app name is not English, Chinese for example, you need to name it in Bundle display name,
Do not name it in TARGETS directly.
Maybe is also works for Japanese and Korean.
I solved this by switching over to Chrome instead of using Safari. Presto, worked right away!
I have met this problem this morning and have solved it. I change my product name from Chinese to English, and write the Chinese name in the Bundle display name, which solve this problem.
You can change the Bundle display name in the info.plist, and change the product name in the General tab in the project.
that's an erratic error. Probably some apple infrastructure problems You may have done something and then it worked - switching your browser, increasing build numbers and the like. But you could've hit several times submit as well. At least, after a while, my submission has been successful.
I opened the iTunes connect on my iPhone , and was able to submit sucessfully via iOS safari. I don't know why.
You will need to change the Build version. Create 1.2 build for version 1.1 of your app. Then upload your binary. After few minutes (on processing) you'll find new build to submit for rewiew.
I spent 2 hours !!!
Finally, i found the solutions. The main culprits is your PRODUCT NAME, it must be in English!
Go to build setting --> packaging --> change your product name into English
Change your "BUndle Display Name" to your desire localized name
Increase your build version and re-upload
This time you're fine!!!
I was plagued with these errors over and over when adding new screenshots.
Nothing seemed to help.
Then I visited iTunes connect in Safari (I normally use Chrome) and somehow all errors went away.
Maybe related to a Chrome browser extension like AdBlock?
TLDR; use Safari for iTunes Connect
I experienced this submitting an update today to my app. For about 30 minutes I retried and received the same error. I tried, removing the binary, signing out, I also rebuilt the binary with an incremented "Bundle Version String".
None of these steps made any difference, but I continued to retry, continued to get the same error, and eventually it accepted the submission.
I don't believe any of these solutions I tried made any difference. I believe there was some internal error on itunesconnect. As the message suggests, I think all you should do is try again later...
I only need to clear all my cookies, instead of switching browser.
Switch the browser you are using & then remove the build, save that once & then again add the build to it & then again save it. After that click on submit for review & it will work perfectly.
After 3 day, Itunes accept my first binary. I have tried to change my Bundle Display Name to English then tried to change to keep version 1.0 and change build versiyon to 1.2. Tried a lot of think and after 3 days surprise!!! Apple accept
I also got this error. Solution I found was to change contents in "Name" section of app description in iTunes Connect.
There was no need to change app name to English language (as some suggest), I just removed ":" character from app name - and then I could submit it to review! My localized versions of application still contained non-English names.
Had the same problem since my application name contains ":". The iTunes connect server returns 500 error because of it. I've just temporary removed ":" from English app title, submitted app and returned ":" back.
I think it ended up being a combination of several factors, but one thing that was definitely wrong was that I hadn't clicked the box about posting info to the Korean store. This was off by default and needed to be clicked. After doing this and several version changes (ended up submitting 1.2 instead of 1.0!) my app finally went into "waiting for review...".
Tried all possible solutions Chrome and Safari; none of them worked.
Then I switched to Firefox and magically it went through.
I found the simple solution. Just go to detail of the version, remove the current build then save.
Then click on the blue add button and add the current build again, save again. Then submit again.
It work for my case. Hope it helps
Log out from the iTunes from the current browser. and Login to iTunes from the another browser and try to submit the app.
Hope it works!
And Make sure that there should not be the Redundant binary (in other words the build number of the binary should not same).
I've just had the same problem.
Switching browsers to Chrome fixed it for me straight away, so will try clearing out Safari, and re-booting in order to get back to submitting with Safari.
#rayg - and for the sake of others - the Korean checkbox doesn't have to be checked in order to succeed in getting the app up for review. Maybe under certain circumstance it does have to be selected, so I'm not saying your solution to your scenario is wrong, but the post gave the impression that it's a requirement for every submitted app, which it isn't.
I have tried above all recommended solutions but none of them worked for me .
Then I select build version from my mac system and logged itunes connect using firefox from window system and it worked for me.
Or you can try itunes connect login from another Window/Mac system.