Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

I'm invited to a team to build an in house app. I'm granted as a team admin in Apple Developer Portal. The problem is that when I want to export the achieved app to a .ipa, it shows the message "Wildcard App IDs can not be used to create In House provisioning profiles. Please use an Explicit App ID." as the following screenshot. At the beginning, I login to Xcode/Preference/Account and download all provisioning profiles. Then I tried to login another account (who is able to export the .ipa) on Xcode/Preference/Account. Both trial lead to a same error message. Then I reset all my certificates and provisioning profiles on developer portal but in vain. The interesting thing is that there's always a wildcard app id "*" on the developer portal, I tried to remove it manually but it comes back every time when I try to export the in house app.

I also tried the answers Xcode 7.2: Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles and this one XCode export app, wildcard error , nothing happened.

Any idea? Thanks for reading my question. I've already spend two days on this issue..... Screenshot1

like image 875
Neo Avatar asked Nov 08 '22 19:11

Neo


1 Answers

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

like image 124
user2571947 Avatar answered Nov 14 '22 21:11

user2571947