Build error: Signing for "gRPC-C++-gRPCCertificates-Cpp" and "VK-ios-sdk-VKSdkResources" requires a development team
Error produced when running benchmark.sh.
** BUILD FAILED ** error: Signing for "gRPC-C++-gRPCCertificates-Cpp" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'gRPC-C++-gRPCCertificates-Cpp' from project 'Pods') warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'BoringSSL-GRPC' from project 'Pods')
error: Signing for "VK-ios-sdk-VKSdkResources" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'VK-ios-sdk-VKSdkResources' from project 'Pods')
System Version: 12.6 Xcode 14.0.1 Hardware Overview Model Name: MacBook Air Model Identifier: MacBookAir10,1 Total Number of Cores: 8 (4 performance and 4 efficiency) Memory: 16 GB
Seems like the problem is that CODE_SIGNING_ALLOWED of resource bundle is being set to YES by default in Xcode 14 while previously it was set to NO in Xcode 13.x. This has been an issue since Xcode 14 beta release up till the public release.
This has been publicly discussed on various forums:
- Xcode 14 build failed with manual code sign and app resource bundles #11402
- Xcode 14 resources bundle "CODE_SIGNING_ALLOWED" being set to YES
Potential fix for this will be to add the following to Podfile to explicitly set code signing to NO.
post_install do |pi|
pi.pods_project.targets.each do |t|
t.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = minimum_target
config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
end
end
end
Will be submitting a PR for these changes shortly to fix this issue.