Xcode couldn't find any provisioning profiles matching

Question

I am trying to rebuild an ios app, that previously had no issues (first rebuild in 6 months or so). Environment is OSX 10.13.5 with all the latest updates, Xcode 9.4.1, Ionic is 3.20.0. Local cordova, ionic and node modules have been updated.

These plugins:

cordova-plugin-device
cordova-plugin-file
cordova-plugin-file-transfer
cordova-plugin-splashscreen
cordova-plugin-whitelist
cordova-plugin-x-socialsharing

Configured for manual signing. Provisioning profiles have been regenerated, with new certs, downloaded and installed (numerous times).

I cannot make this error go away in either debug or release builds:

Check dependencies Code Signing Error: No profile for team ‘8SEBNER3XM’ matching ‘ABM 2018 Dev’ found: Xcode couldn’t find any provisioning profiles matching ‘8SEBNER3XM/ABM 2018 Dev’. Install the profile (by dragging and dropping it onto Xcode’s dock item) or select a different one in the General tab of the target editor. Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.4’

** ARCHIVE FAILED **

The following build commands failed: Check dependencies (1 failure) Error: Error code 65 for command: xcodebuild with args: -xcconfig,/Users/kerickhowlett/Documents/PhoneProjects/ABM/platforms/ios/cordova/build-debug.xcconfig,-workspace,Cocktail Pro.xcworkspace,-scheme,Cocktail Pro,-configuration,Debug,-destination,generic/platform=iOS,-archivePath,Cocktail Pro.xcarchive,archive,CONFIGURATION_BUILD_DIR=/Users/kerickhowlett/Documents/PhoneProjects/ABM/platforms/ios/build/device,SHARED_PRECOMPS_DIR=/Users/kerickhowlett/Documents/PhoneProjects/ABM/platforms/ios/build/sharedpch

Despite what the message says, there is what seems to be perfectly valid provisioning profiles in both Xcode project General tab, and Build Settings (ie 'ABM 2018 Dev'). They match the files in Library/MobileDevice/Provisioning Profiles folder. The team id is verified as correct. The profiles been regenerated / re-installed many times. Xcode thinks they are valid from within Xcode (does not complain). Running as ‘ionic cordova build ios’ seems to have a different opinion, and complains about the profiles. Similar error with --release added to the command. Based on trial and error, it is the PROVISIONING_PROFILE_SPECIFIER that seems to be the issue. I've tried a number of variations but always get the same error, which seems bogus. I have tried both profile names and UUID's.

What am I missing?

Answer 1

I had the same problem with signing and just didn't realise that you do not only have to deactivate the options for iCloud and Push Notifications under Signing & Capabilities but rather delete them by clicking the trash right next to them. Took me way too long to figure this out.

Answer 2

Change the device to a Simulator or Real device will fix the issue

Answer 3

Mine was similar, I just needed to sign back into Apple Developer ID. My login had expired. Xcode -> Settings->Accounts. This happened due to my certificate expiring. Select Manage Certificates and hit the plus icon on the lower left.

Answer 4

On iPhone: Settings / General / VPN & Device Management / choose your developer profile / click "trust this developer"

Answer 5

ionic cordova build ios —prod

Even with provisioning error you can still build the app

Then go Xcode —> Product —> Build For —> Profiling

Worked fine for me !!

Answer 6

First of all, you need check your Bundle Identifier. It'd be unique. If you have Bundle Identifier as 'example, etc.' you need to change that identifier. After try again. Most likely there is no problem with the certificate

Answer 7

I thought it would be hard to solve, but all I had to do was to go to Signing & Capabilities and Select team: 'None' and then select the correct team again.

Answer 8

Go to Xcode, Your project, Signing and Capabilities tab and choose the correct team and sign in with your apple id

Answer 9

For me the issue was that my Xcode session was disconnected. Few weeks ago, I had to renew my licence to Apple Developer Program, maybe this was the origin of the issue.

To sum up, I went to xCode -> Preferences -> Account -> Log in again

My certificates were then reloaded to my Xcode

Answer 10

You can get this issue if Apple update their terms. Simply log into your dev account and accept any updated terms and you should be good (you will need to goto Xcode -> project->signing and capabilities and retry the certificate check. This should get you going if terms are the issue.

Answer 11

What fixed it for me was plugging my iPhone and allowing it as a simulator destination. Doing so required my to register my iPhone in Apple Dev account and once that was done and I ran my project from Xcode on my iPhone everything fixed itself.

1. Connect your iPhone to your Mac
2. Xcode>Window>Devices & Simulators
3. Add new under Devices and make sure "show are run destination" is ticked
4. Build project and run it on your iPhone

Answer 12

I am now able to successfully build. Not sure exactly which step "fixed" things, but this was the sequence:

• Tried automatic signing again. No go, so reverted to manual.
• After reverting, I had no Eligible Profiles, all were ineligible. Strange.
• I created a new certificate and profile, imported both. This too was "ineligible".
• Removed the iOS platform and re-added it. I had tried this previously without luck.
• After doing this, Xcode on its own defaulted to automatic signing. And this worked! Success!

While I am not sure exactly which parts were necessary, I think the previous certificates were the problem. I hate Xcode :(

Thanks for help.

Answer 13

I opened XCode -> Preferences -> Accounts and clicked on Download certificate. That fixed my problem

Answer 14

Requirements:

1. Unique name (across all Apple Apps)
2. Have to sign in while your phone is connected (mine had a large warning here)

Worked great without restart on Xcode 10

Answer 15

Try to check Signing settings in Build settings for your project and target. Be sure that code signing identity section has correct identities for Debug and Release.