Archive validate complains about wildcard app ID, but I'm using an explicit one

Hi, did you find a solution to this?

hi, Im stuck in the same step. plz help

Same issue here, yesterday the export worked well and no setting is changed. Could it be a portal's bug?!

I had this problme today too. And in my case was due to a "Apple Worldwide Developer Relations Certification Authority" cerificate which was expired. In my keychain I had to of them; One good with expiration to 2023 and another one expired. Once I deleted the expired one it worked.

I went through this process, removing the relations certificate. Which seemed promising, but unfortunately still isn't working. 😕

Same issue here! Stuck!!

Same problem here 😟

Updating to 7.2.1 did not make a difference, unfortunately.

Was working fine last Friday and I have created a bunch of enterprise builds before.

I re-did everything from scratch (certificates, keys, appId, provisioning) with the exact same result.

It seems XCode ignores the identifier setting from the specified provisioning profile and auto-generates a wildcard App ID upon exporting archive for enterprise IPA and uses that one instead. You can verify that behavior by looking at your App IDs in the member center.

Notably, when looking at the .plist in the .xcarchive package generated by archiving, I see an explicit bundle identifier. I find the same correct identifier by looking further down at .plist in the .app contained within the archive. Also, when looking at the .mobileprovision file used, it contains an explicit ID as well.

I've triple-checked project and target settings and schemes. It's just not working. This has to be a recent change or portal bug, hope we hear something very soon.

(The solution provided on StackOverflow is not doing anything for me, but might help out someone else: http://stackoverflow.com/questions/35251324/xcode-7-2-failed-to-locate-or-generated-signing-assets-wild-card-app-ids-can-n)

FWIW, I skipped Validate... which for whatever reason, I have always done prior to exporting, for better or worse. And the produced export ipa seems to be signed correctly, and installs normally. So the workaround at this time is just to NOT validate the archive. Just export it for enterprise distribution.

That being said, this Validate issue is clearly a bug even though you can get around it. The fact that it seems to create additional provisioning profiles for you because it cannot find the right one is particularly odd.

I sure hope this also works for you all. It's a very frusterating roadblock.

Thanks for your suggestion. This must be an XCode GUI bug somewhere. (see next post as well)

I've used the xcodebuild -exportArchive command line option and it worked out great as well. Installed the resulting IPA to a few devices and no problems whatsoever.

Very annoying and time consuming issue as the error given probably makes technical sense but doesn't help us out at all.

For those interested in xcodebuild: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/xcodebuild.1.html

I came to this solution through trying to build via command line.

You can go here: https://www.apple.com/certificateauthority/

This is the one you want to use. The previous one expired 2/14/16

WWDR Certificate (Expiring 02/07/23)

I ran into additional problems creating and exporting a valid certificate for our push notification server.

Please double-check you have a single, valid "Apple Worldwide Developer Relations Certification Authority" certificate as outlined in this StackOverflow post: http://stackoverflow.com/questions/35390072/this-certificate-has-an-invalid-issuer-apple-push-services . I thought this was all fine on my side, but I forgot to enable "Show Expired Certificates" in Keychain.

My old certificate expired Feb 14th 2016, explaining why validation also suddenly failed!

Validation is only avalible for apps destined for the App store or TestFlight. If you found it was useful to validate Enterprise applications and want this feature, please file an enhancement request bug report using our bug reporting system <https://developer.apple.com/bug-reporting/>.

this did not help me