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.
I am using xcode 7.1 and trying to upload my app to the app store directly through xcode. While uploading I am getting a weird error:-
cannot verify client 3000
Note:- I recently made changes in the accounts (xcode preference section). Is this related to my error?
I also restart the xcode but issue still there?
I already checked this question on SO, but they say restart your xcode. But this does not solve my problem.
For my case,I got this error after selecting "Generic iOS Device" when archiving, however i plugged in my iPhone and selected it, then archived, I got no errors this time.(I also cleaned both Shift+cmd+k and Shift+alt+cmd+k before archiving)
I encountered the same issue the first time I tried to submit to app store with the target on my device.
What worked for me:
I retried a couple of minutes later without changing a thing and everything went smooth.
This is temporary apple server bug. Try it again OR Retry after some time it will fix the problem.
Thanks
There is no need to reinstall Xcode. Just wait a few minutes and try again and it will work.
I tried :
waiting days,
restarting,
deleting the developer account in
preferences,
submitting archives from a connected device,
submitting
archives from a iOS generic device.
Nothing worked.
I needed to:
create an archive (it was from a connected device),
in the organiser window select the export button (on the right hand side underneath the "Upload to App Store" button.
Select that the export is for app store distribution.
Wait.
Take a note of the location the .ipa file is saved to.
Go back to Xcode, then select the menu item Xcode > Open Developer Tool > Application Loader.
Select Deliver Your App, and select choose.
Navigate to your .ipa file noted above.
Select next, wait, next, check for any error message, send.
Hope this helps someone.
I got this error while uploading my distribution archive to App Store with selecting Distribution provisioning profile scheme -> Product -> Archive -> Upload to App Store. The error is based on I chose my real iphone device in Xcode by mistake. You need to choose "Generic iOS Device" and repeat same steps as I mentioned before.
You have to plug in your iPhone to your Mac and try to upload to AppStore again.
For some reason, validating the archive before uploading fixed the issue for me.
With Xcode 7.1, I could only make a successful build without bitcode. Try it out if everything else fails.
I resolved this by exporting ("export" in xcode archive organizer -> "to iOS App Store") and using the Application Loader instead of xcode to submit.
It is recurring. Seems to me like an internal error with apples identification service or so.
My definite solution:
Get yourself a cup of tea and try it again.
You can, of course, do some voodoo or change the target device or something, but re-trying after a while will do.
I have the same issue.
I did the below steps:
Step 1: Select Code Signing Identity for "Release"
Step 2 : Select Distribution profile
I tried to use Application Loader instead and it worked well. Maybe that helps
I've been having this problem since Xcode 7.1 (for more than a month). I did everything I could trying to solve this: restart Xcode, clean project, clean build folder, build with a device connected, reinstall Xcode multiple times, even formatting the whole disk and starting from scratch. None of this worked.
During this time my colleague was always able to upload the very same builds to App Store without any problem.
Curiously, what solved this problem for me was disconnecting my non-Apple wireless mouse.
I found this out when I tried to submit an app from my home computer and got the same error. I disconnected the mouse dongle, tried again and it went through.
I've verified this three times both on my home (MacBook Pro 2013) and work computer (Mac Mini 2014).
This leads me to believe that during the app submission process Apple may check if your environment is purely made by Apple or not, and may block your submission based on that. This would explain the "Cannot verify client" message.
This one worked for me:
Delete the Archive that failed during upload.
Clean the solution.
Rebuild the solution.
Archive the it.
Go to Xcode's Organizer, then Validate (this should be 'Successful').
Upload the build.
I am using xcode 7.1 and trying to upload my app to the app store directly through xcode. While uploading I am getting a weird error:-
cannot verify client 3000
Note:- I recently made changes in the accounts (xcode preference section). Is this related to my error?
I also restart the xcode but issue still there?
I already checked this question on SO, but they say restart your xcode. But this does not solve my problem.
For my case,I got this error after selecting "Generic iOS Device" when archiving, however i plugged in my iPhone and selected it, then archived, I got no errors this time.(I also cleaned both Shift+cmd+k and Shift+alt+cmd+k before archiving)
I encountered the same issue the first time I tried to submit to app store with the target on my device.
What worked for me:
I retried a couple of minutes later without changing a thing and everything went smooth.
This is temporary apple server bug. Try it again OR Retry after some time it will fix the problem.
Thanks
There is no need to reinstall Xcode. Just wait a few minutes and try again and it will work.
I tried :
waiting days,
restarting,
deleting the developer account in
preferences,
submitting archives from a connected device,
submitting
archives from a iOS generic device.
Nothing worked.
I needed to:
create an archive (it was from a connected device),
in the organiser window select the export button (on the right hand side underneath the "Upload to App Store" button.
Select that the export is for app store distribution.
Wait.
Take a note of the location the .ipa file is saved to.
Go back to Xcode, then select the menu item Xcode > Open Developer Tool > Application Loader.
Select Deliver Your App, and select choose.
Navigate to your .ipa file noted above.
Select next, wait, next, check for any error message, send.
Hope this helps someone.
I got this error while uploading my distribution archive to App Store with selecting Distribution provisioning profile scheme -> Product -> Archive -> Upload to App Store. The error is based on I chose my real iphone device in Xcode by mistake. You need to choose "Generic iOS Device" and repeat same steps as I mentioned before.
You have to plug in your iPhone to your Mac and try to upload to AppStore again.
For some reason, validating the archive before uploading fixed the issue for me.
With Xcode 7.1, I could only make a successful build without bitcode. Try it out if everything else fails.
I resolved this by exporting ("export" in xcode archive organizer -> "to iOS App Store") and using the Application Loader instead of xcode to submit.
It is recurring. Seems to me like an internal error with apples identification service or so.
My definite solution:
Get yourself a cup of tea and try it again.
You can, of course, do some voodoo or change the target device or something, but re-trying after a while will do.
I have the same issue.
I did the below steps:
Step 1: Select Code Signing Identity for "Release"
Step 2 : Select Distribution profile
I tried to use Application Loader instead and it worked well. Maybe that helps
I've been having this problem since Xcode 7.1 (for more than a month). I did everything I could trying to solve this: restart Xcode, clean project, clean build folder, build with a device connected, reinstall Xcode multiple times, even formatting the whole disk and starting from scratch. None of this worked.
During this time my colleague was always able to upload the very same builds to App Store without any problem.
Curiously, what solved this problem for me was disconnecting my non-Apple wireless mouse.
I found this out when I tried to submit an app from my home computer and got the same error. I disconnected the mouse dongle, tried again and it went through.
I've verified this three times both on my home (MacBook Pro 2013) and work computer (Mac Mini 2014).
This leads me to believe that during the app submission process Apple may check if your environment is purely made by Apple or not, and may block your submission based on that. This would explain the "Cannot verify client" message.
This one worked for me:
Delete the Archive that failed during upload.
Clean the solution.
Rebuild the solution.
Archive the it.
Go to Xcode's Organizer, then Validate (this should be 'Successful').
Upload the build.
I have been trying to take advantage of Xcode now allowing developers to test on devices without being enrolled on the developer program.
This was working just a few weeks ago, no problems at all
however, for no apparent reason, I am getting this error message whenever i try to run my app on the iPhone:
after some googling a website led me to this page in the settings app:
From what i can gather on google, The problem is that the app isn't verified. However when i click verify nothing changes. The text at the top of the screen changes very briefly (i assume it's saying loading)
I have tried deleting the provisioning profile, that Xcode had created, and clicking fix when Xcode tells me it can't find the profile. Nothing changed
so my question is: does anybody know what the problem is here and how to fix it?
I've never seen a problem with that before but with x-code there are usually 3 really annoying but normally foolproof steps to solving a problem such as this.
1) Update your IOS and make sure you are on the most recent version
2) Reinstall X-code
3) Recreate the app
Like I said those 3 steps can normally solve any non code related problem.
Hope that helps!
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