Xcode Export App, Wildcard Error

XCode export app, wildcard error

I faced the same problem and almost spent one day to solve the problem.

When I encountered the problem, I thought it was an error related with invalid distribution certificate or provisioning profile. I renewed certificates and all other stuff. Nothing worked! Neither certificates nor provisioning profiles were the root cause.

I have seen an announcement on Apple Developer page. Apple's WWDR Certificate was expiring and newest one available on that page. I updated that certificate and it worked!

Steps you should follow:

  1. Open Keychain Access and remove expired Apple Worldwide Developer Relations Certification Authority from certificates.
  2. Download new certificate as suggested.
  3. Be sure that Apple Worldwide Developer Relations Certification Authority is located under Systems keychain, not in login.
  4. Open XCode (If already, close and then open)
  5. Clean your project.
  6. Select your valid signing certificates and provisioning profiles. (You don't need to refresh your certificates or profiles as annoucement suggested)
  7. Hit Archive button!

Hope this may help someone else.

Wildcard App IDs can not be used to create In House provisioning profiles. Please use an Explicit App ID

Xcode unable to create distribution builds for App Store submissions or Enterprise apps.

This issue occurs when the expired WWDR Intermediate certificate is present in both the System keychain and Login keychain within the Keychain Access application.

To resolve the issue, first download and install the renewed certificate.

Next, in the Keychain Access application, select the System keychain.

Select 'Show Expired Certificates' in the View menu and then delete the expired version of the Apple Worldwide Developer Relations Certificate Authority Intermediate certificate.

Your certificates should now appear as valid in Keychain Access and be available to Xcode. This issue is resolved in OS X El Capitan v10.11.4 beta.

from developer.apple.com

Xcode 7.2: Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles

It seems like it is bug in Xcode 7.2 , after trying multiple times and troubleshooting , below solution worked for me.

1) Open Xcode preference

2) Select the team

3) Click the "View Details.."

4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.

5) In section "Provisioning Profiles". Click on "Download All".

6) Restart the Xcode.

7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.

For more detail find Screenshots below:

1) Open Xcode preference,

Sample Image

2) Select the team,
Sample Image

3) Click the "View Details..".

4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.

Sample Image

Delete Provisioning Profiles
Sample Image

5) In section "Provisioning Profiles". Click on "Download All".

Sample Image

6) Restart the Xcode. (most of the times Restarting Xcode is only solution after downloading new provisioning profiles or after changing App identifiers)

7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.

Hope it solves your problem. :)

P.S: I've also opened a bug to Apple via Apple Bug Reporter.

iOS Enterprise Build - Cannot use wild card

It seems like it is bug in Xcode 7.2 , after trying multiple times and troubleshooting , below solution worked for me.

1) Open Xcode preference

2) Select the team

3) Click the "View Details.."

4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.

5) In section "Provisioning Profiles". Click on "Download All".

6) Restart the Xcode.

7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.

For more detail find Screenshots below:

1) Open Xcode preference,

Sample Image

2) Select the team,
Sample Image

3) Click the "View Details..".

4) In section "Provisioning Profiles": Right Click on any profile and Show in Finder and Delete All Provisioning Profiles in that folder.

Sample Image

Delete Provisioning Profiles
Sample Image

5) In section "Provisioning Profiles". Click on "Download All".

Sample Image

6) Restart the Xcode. (most of the times Restarting Xcode is only solution after downloading new provisioning profiles or after changing App identifiers)

7) Select Team in General, and Provisioning Profiles in Build Settings and archive build again.

Hope it solves your problem. :)

P.S: I've also opened a bug to Apple via Apple Bug Reporter.

Issue with signing app with wildcard profile

TL;DR:
Find out what the client's (provisioning profile's) entitlements are and make sure you match them.

The error is trying to say that the entitlements in your provisioning profile and their provisioning profiles differ. The difference could be a keychain group, push notification environment or something else.

The reason why Xcode asks you to choose a provisioning profile twice (once when archiving, once when distributing) is that all the provisioning profile entitlements are picked up in archive stage and mostly ignored in the distribution stage.

This makes it all too easy to distribute with the wrong entitlements, especially if your archive stage accidentally picked up a wildcard profile. Not your case, but that's why you should burn wildcard profiles with fire.

There are clever re-signing scripts (a.k.a. "Distribute..." button replacements) that will try to make the entitlements right by mashing what they find in the end user provisioning profile into your binary but I think the best solution is to make sure your provisioning profile's entitlements and any extra entitlements you add to your app matches their provisioning profile's.

I find Xcode's provisioning profile/entitlement system to be error prone. On hand you have entitlements that are basically part of your app's identity and may as well be set in stone (TODO: make your CI server check them). And on the other hand you have Xcode's build phase gleefully changing your app's entitlements based on its automatic/random provisioning profile selection. Silly.

Missing Provisioning Profile error when archiving using xcodebuild

What has finally worked is to remove wildcard while mentioning the App id in the exportOptions.plist file.

<?xml version="1.0" encoding="UTF-8"?>
<dict>
<key>provisioningProfiles</key>
<dict>
<key>APP_ID_WITHOUT_WILDCARD_CHAR</key>
<string>PROVISIOING_PROFILE_NAME_AS_SEEN_BY_XCODE</string>
</dict>
<key>method</key>
<string>app-store</string>
<key>signingCertificate</key>
<string>iPhone Distribution</string>
<key>signingStyle</key>
<string>manual</string>
<key>stripSwiftSymbols</key>
<true/>
<key>teamID</key>
<string>TEAM_ID</string>
<key>uploadSymbols</key>
<true/>
</dict>
</plist>


Related Topics



Leave a reply



Submit