I am uploading iPhone application using latest xCode 8. I have good internet connection and all the relevant settings set up at iTunes connect. My distribution profiles are also set up correctly.
I am facing below error:-
iTunes software service authentication error domain error 434
So this has what worked for me:
Preface:
4 days of debugging, recreated certificates numerous times, nothing worked, every time i try to validate/upload via Xcode it says same error "iTunes software service authentication error domain error 434"
Solution without XCode:
Create archive in Xcode
Export IPA in Organiser (Xcode > window > Organiser)
Open Application Loader and manually choose IPA generated
Done
Solution with XCode:
Create archive in Xcode
Click Validate
Unselect BitCode
Check if its validated, mine got validated when i unchecked bitcode
Not Try to genrate similar fashion with Bitcode unselected
If all goes fine now generate with Bitcode Checked(mine worked with these exact steps)
Done
This is a very common error while uploading a build to iTunes Connect.
A simple answer to it : "Just RETRY".
To resolve this error follow these methods.
If you have not added app icons add them and try archiving.
Remove developer account and add account again. Press CMD + , to bring up preferences in Xcode and from accounts remove and add back account. Try archiving this.
Clean project (CMD + Shift + K), close Xcode, restart Xcode and
build project (CMD + B). Check for warnings. ( if you are using
cocapods some times Xcode asks you to change project settings in
warning. Click on warning and fix it. Xcode fixes it automatically)
Simply retry archiving.
ToDo. Add More solutions
In my case the problem was the virus protection software I am using. I turned it off before attempting validation and everything went fine.
This could be the problem of Xcode. You can try two different approaches here.
i) Use Application loader, Download it.
ii) Before using Application Loader please un-install all certificate and upload the ipa file. If it fails via app loader.
then second approach we can use try to upgrade the version of Xcode. Either de-grade it (xcode 7.X) or upgrade it (8.X) some time with some specific version of xcode and and specific version of OS system throw such error.
Try using those hopefully second one can help you to upload the app.
Change the network connection and application submit via Application Loader
Did you set the device to Generic iOS Device before you archived the build? That appears to have fixed it for me on a couple of different occasions.
I got exactly the same error response, read a bunch of posts like this that were uncertain of cause & solution, tried to validate it again with zero changes, and it validated successfully. Go figure...
I had this same issue, but it turned out I used a different profile in the Xcode project, then when I tried to validate the app. It wasn't noticeable since at my company we use multiple Apple id's under the same businessname. Maybe checking this helps?
None of the solutions here worked for me but I was able to solve these errors executing the application on the device that is connected to the computer before archiving it. I tried to archive it again and the validate process was passed.
None of the answers worked for me. Following steps helped me fix it.
Quit the Xcode
Delete all provisioning profiles (/Library/MobileDevice)
Start the code and try to validate without download the provisioning profiles.
The xcode will download the profiles for you.
In my case I had 2 builds in the same app and when I tried to verify one of them it started giving the same error. I removed both builds and re archive. It worked fine after that.
In my case, I have checked iOS provisioning profile from developer website and found the one related to my app was invalid.
I have regenerated (all invalid) provisioning profiles and download it from xCode -> preferences -> accounts. This resolves my case.
I have a different solution. I had "Enable Bitcode" set as false in my target settings but had "Include bitcode" checked as true for the validation. For obvious reasons, the validation would fail every time if I had include bitcode checked. I unchecked include bitcode and it worked just fine after cleaning my project.
it is quite easy, quit and reopen the Xcode project clean the project change the build number and build an archive.it will work
Related
I manually deleted my app from the iPhone and now I get this error message when trying to run it again from Xcode.
I cleaned the build folder, restarted the device, Xcode and the Mac, nothing helps.
I also tried everything that's mentioned here: Install claimed to have succeeded, but application could not be found on device
How do I force a re-installation?
As always, when the question is posted on SO, one finds a solution ;)
I edited the Scheme, setting the build configuration from debug to release and that installed the app again. Changed it back to debug and now it's running again as expected.
I ran into the same issue while testing a app on iOS 13 via XCode 11.0. Building via the legacy system solved it (File > Workspace Settings... > Build System > Legacy Build System).
Hope it helps
I had a similar issue after one of Carthage/XCode updates. It means iOS was not able to install app on the phone. XCode apparently is not able to provide this information directly. The first thing to do is open your phone console - go to Window/Devices and Simulators then select your device and click Open Console. In the console you can search for your app name what should provide you more detailed fail info. In my case it was sth like this:
Applications did fail to install: (
"<LSApplicationProxy: 0x118913b60> com.mydomain.myapp (null) <com.mydomain.myapp <INVALID >:0>"
) (appInfos: (null))
There was another console log few rows before flagging the problem:
0x16f4df000 -[MIExecutableBundle codeSigningInfoByValidatingResources:performingOnlineAuthorization:ignoringCachedSigningInfo:checkingTrustCacheIfApplicable:error:]: 789: Code signing identifier (org.alamofire.Alamofire.iphonesimulator) does not match bundle identifier (org.alamofire.Alamofire.iphoneos) for /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.E83T1l/extracted/myapp.app/Frameworks/Alamofire.framework
There was an issue with one of the frameworks Alamofire I'm using in the project. I changed bundle identifier of the project and build framework again what solved the problem.
Hope it helps!
In my case, the problem was an embedded framework that was not being signed. In the General tab of the project settings, setting the embed setting to 'Embed & Sign' did the trick.
In my case it was a problem with new Development certificate. It's created automatically after Xcode updated to 11 and may not be included in current provisioning profile.
I was facing similar issue in Xcode 11.1. I have fix this issue. Not sure about this solution that it will to work for all or not.
My device iOS version was older then the iOS Xcode target build version.
Steps:
I have put Xcode target Device to iPhone device OS version.
Delete derived data
Start xcode and open project
Clean the project and gererate build and install in device
Note: Please check your developer account, certificate validation and already registered device warning.
Hope this solution will help some peoples. Happy coding.
After trying everything here, for me the solution was to change my distribution profile to use the new Apple distribution certificate that covers all apple platforms. This should be compliant with xcode 11 (if you're not experiencing one of the other million problems since the "upgrade").
The cert change is mentioned here:
https://developer.apple.com/documentation/xcode_release_notes/xcode_11_release_notes
Cert creation instructions here:
https://help.apple.com/developer-account/#/devbfa00fef7
Once done, make sure the correct profile is selected in Signing & Capabilities, and 'Apple Distribution' is selected under Build Setting -> Signing for the appropriate build configurations
A solution that solved this issue for me was to check the signing team for my tests target. Selecting the same development team then meant that my app was able to be built and run on device.
Build system: New Build System
Xcode: Version 11.1
Uninstall all the other apps that are under the same "Organization" or "Bundle Identifier" with your current app and try again.
It works for me. Hope it does for you too.
On your iPhone go to Settings/General/Profiles & Devices/Apple Development: "YOUR APPLE ID" and delete all apps from there. It fixed the problem for me.
It happened to me when trying to launch a watchOS app on a real device.
The only solution that worked was:
Delete iOS app from device
Delete watchOS app from device
Close and reopen Xcode
Clean build folder
I did a Product -> Clean then Build, and it was able to run.
Go to settings on your phone and wipe out all certificates and apps and then install your app again. That helped me
Problem occured on XCode 11
TL;DR:
Try changing Embed option in General=>Section Frameworks, Libraries.. to Do Not Embed (although it sounds strange)
In my General=>Section Frameworks, Libraries.. list are Security.framework and the CocoaPods Pods_projectname.framework amongst others. Default setting of these two was Do Not Embed. Sounded strange to me, so I changed it without need alternating to Embed & Sign or Embed Without Signing. With both options the error occured!
On your iPhone go to Settings/General/Profiles & Devices/Apple Deelopment: "YOUR APPLE ID" and delete all apps from there. It fixed the problem for me.
This was the solution that worked for me.
Please double check the bundle ID of the installed application to see if it is re-applied, this will also cause this problem .I uninstall the app and solve the problem.
In my case i have PROD certificate and trying to install the app in the device, later i changed to development certificate it got installed.
As Marcin's answer suggested, I visited the phone console and in my case, it is this error message:
-[MIFreeProfileValidatedAppTracker _onQueue_addReferenceForApplicationIdentifier:bundle:error:]: 182: This device has reached the maximum number of installed apps using a free developer profile: {(
So if you are signing your app with a Personal Team certificate, make sure that you don't have more than 3 apps.
Read more here: Why can I not install more than three apps?
As for me,
I added a custom key-value to Info.plist of main watchOS application file. That was wrong.
After removing it, all works correctly.
It seems this is not allowed but where is no other information about it.
If you have other under-development apps installed, try uninstalling those you are not using, and run Xcode to install your app again. It works for me.
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.
2 days before I successfully uploaded the archive for my application and my application is on app store, but yesterday and today when I upload the archive I see "Uploading the archive" message (with subtitle "Sending api usage to itunes connect") at the beggining, but then I see "iTunes Store operation failed. This action couldn't be completed. Try again later" :
When I try to upload the archive for another application, everything is OK, it's very strange, because since 2 days ago I only changed the minimum age in the application from 17 to 18 (so I didn't change everything important in the application settings).
May be in happen because we use iAd network and apple notified that this network will be unavailable since July ?
just upload the ipa with Application Loader 2.9.1, even thought the apple tell you that you should upload the ipa with xcode 7.2 or Application Load 3.0.0, but , my solution works well
download Application Loader 2.9.1
Try this
Xcode -> Open Developer Tool -> Application Loader -> Login with AppleID -> Choose your app IPA
may this help you
Another solution that might help is disabling bitcode when submitting the IPA through XCode. Not sure why but this worked for my colleague when he had the same issue. If you want to keep bitcode then Application Loader will work, as pradip kikani pointed out.
I saw this exact problem TWICE yesterday (14th April 2016) using Xcode 7.2.
I'd get either a
"This action couldn't be completed. Try again later"
or a
"This action couldn't be completed. Try again. (-22421)"
which one appeared to be random. I just kept trying and trying and eventually the upload succeeded in both cases. Apple are obviously being a bit ****.
Not the most technical useful answer but thought it worth mentioning.
I ran into the same issue today when I wanted to validate my app in Xcode 7.3.1. In my case, my provisiong profiles had all expired on May 01, 2016 as I found out in the Xcode "Preferences > Accounts > View Details". I clicked on "Download All" and got renewed profiles with an updated expiry date.
I tried restarting my mac and all that but nothing helped.
What actually worked for me :
Logged out from my developer account in Xcode preferences.
Turn off bitCode from build settings.
Changed the provisioning profile.
But im not sure which one of the methods worked cause i did them all at ones.
good luck.
Got Same issue today!! I found there is no "arm64" in my valid Architectures.instead there was one "arm6".
Updated Valid Architecture list resolved my problem.
While facing such issue you should take care of some points listed below:
Make sure you have added correct bundle ID & provisioning in to App
If it is correct than might be after updating it on developer account it was not updated on Xcode. So in that case go to Xcode > Preferences > remove Account & Add it again. Clean Xcode set provisioning in targets & Projects both
Once you done with above steps clean project & Prepare New Archive again & try to submit it
Important Notes:
Do not try to submit Build files from Beta Xcode versions
If you are using Application loader than make sure its version is greater than or equals to 3.0
Hope it will help you.
I solved a similar issue by changing the build number from 1.0 to 1.1.
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.