This error is related to how CocoaPods expects code signing configurations for frameworks.
=== CLEAN TARGET Pods-Xxxxxxxxx OF PROJECT Pods WITH CONFIGURATION Release === Check dependencies [BEROR]Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found. [BEROR]CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.1'
A wildcard development provisioning profile
When Xcode performs an initial code signing (when it compiles the framework projects), it requires a certificate and provisioning profile which can be used for signing the CocoaPods framework projects.
On your Mac, you most likely have your own Development certificate and Wildcard team provisioning profile, which is enough for Xcode to do the initial code signing for the framework projects.
So upload these (Development identity/certificate (.p12) and the Team wildcard provisioning profile) to bitrise.io. Xcode will do an initial code signing with the development signing files, and then it’ll resign the archive when it exports the final IPA.
Modifying code signing settings through
One of our beloved users sent us the following fix for this problem. Add the following script as a
Post script to your
post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = "" config.build_settings['CODE_SIGNING_REQUIRED'] = "NO" config.build_settings['CODE_SIGNING_ALLOWED'] = "NO" end end end
- You can find a related CocoaPods issue and discussion at: https://github.com/CocoaPods/CocoaPods/issues/4331
- You can also find possible solutions at CocoaPod’s official GitHub issues page, like this one: https://github.com/CocoaPods/CocoaPods/issues/3063.