Reputation: 2221

Strange Errors on Archive Validation

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!

Upvotes: 48

Answers (16)

Alex Stylianos

Reputation: 84

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.

Upvotes: 0

Xavi Esteve

Reputation: 1162

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)

Upvotes: 0

Sour LeangChhean

Reputation: 7409

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.

Upvotes: 0

Timothy L.J. Stewart

Reputation: 1754

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.

Upvotes: 1

Paul S G

Reputation: 11

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

Upvotes: 1

Shah Nilay

Reputation: 798

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.

Upvotes: 2

Thongchai S.

Reputation: 1

1.Cmd+Shift+K 2.Close Xcode 3.Open Xcode 4.Cmd+B 5.Product->Archive

enter image description here

Upvotes: 0

M Hamayun zeb

Reputation: 508

I solved it by uploading my app through Application Loader.

Archive app Export ipa iOS Deployment
Xcode-> open developer tool -> Application loader

Upvotes: 1

Hari c

Reputation: 1159

I Got the same issues when i try first time.Next time it Validated successfully. Please check network once before trying second time.

Upvotes: 0

nurnachman

Reputation: 4565

Bump the build number and validate again.

Upvotes: 5

harry

Reputation: 338

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.).

Upvotes: 3

AtWork

Reputation: 1293

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.

Upvotes: 8

tishu

Reputation: 1008

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.

Upvotes: 0

Anatolii Pazhyn

Reputation: 1472

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.

Upvotes: 1

Grigory Konovalov

Reputation: 169

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).

Upvotes: 0

Trần Đức Trịnh

Reputation: 59

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!

Upvotes: 0

Strange Errors on Archive Validation

Answers (16)

Clicked Valid until it succeeded, 3rd time.

Related Questions