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?
3. How To Fix Xcode Failed To Create Provisioning Profile Error. To fix this error is very easy, just connect your real iOS device such as iPhone to the Mac computer with a USB line, follow the popup screen on the iPhone, then you can select your iOS device in the Set the active scheme drop down list.
If your Bundle Identifier has a name like "com. myapp. app1", you will get this error: Could not find any available provisioning profiles for iOS, because your profile accept only apps with the names started with com. companyname and you are using a appname different.
All the provisioning profiles are present and Xcode Archives it successfully when you do 'Product > Archive'. ...... .... .. INFO [2018-10-01 21:06:36.47]: ▸ error: No profile for team 'XXXXXXXXX' matching '< AppStore provisioning profile>' found: Xcode couldn't find any provisioning profiles matching 'XXXXXXXXX/< AppStore provisioning profile>'.
Xcode couldn't find any iOS App Store provisioning profiles matching '<bundle_id'>" Currently using: Xcode Version 13.0 (13A233). Mac 11.6
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’
Without a paid Developer account, Xcode will not be able to generate the proper provisioning profile that includes the In App Purchases capability. Please try removing the In App Purchases feature from the configuration of your Xcode project. Then Xcode should be able to handle provisioning profile generation for you.
I am now able to successfully build. Not sure exactly which step "fixed" things, but this was the sequence:
While I am not sure exactly which parts were necessary, I think the previous certificates were the problem. I hate Xcode :(
Thanks for help.
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With