Deployment issue migrating to CircleCI 2.0 for XCode 9.2


#1

Hi Team,

We are facing issues migrating to CircleCI2.0 with XCode 9.2.
However it works fine with CircleCI1.0 with XCode9.0.

Please find the error log below.
±--------------±----------------------------+
| Build environment |
±--------------±----------------------------+
| xcode_path | /Applications/Xcode-9.2.app |
| gym_version | 2.68.1 |
| export_method | enterprise |
| sdk | iPhoneOS11.2.sdk |
±--------------±----------------------------+

[02:12:19]: ▸ Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.2’
[02:12:19]: ▸ Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.2’
[02:12:19]: ▸ Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.2’
[02:12:19]: ▸ Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.2’
[02:12:19]: ▸ Code Signing Error: Code signing is required for product type ‘Application’ in SDK ‘iOS 11.2’
[02:12:19]:
[02:12:19]: :arrow_up:️ Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error

regards,
Rajesh Panda


#2

What does it say in the output of the command recommended in the last line?


#3

:arrow_up:️ Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error
[13:47:48]: :clipboard: For the complete and more detailed error log, check the full log at:
[13:47:48]: :clipboard: /Users/rajeshpanda/Project/banking-app-ios/fastlane/logs/NedBankApp-NedBankApp.log
[13:47:48]:
[13:47:48]: Looks like fastlane ran into a build/archive error with your project
[13:47:48]: It’s hard to tell what’s causing the error, so we wrote some guides on how
[13:47:48]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
[13:47:48]: Before submitting an issue on GitHub, please follow the guide above and make
[13:47:48]: sure your project is set up correctly.
[13:47:48]: fastlane uses xcodebuild commands to generate your binary, you can see the
[13:47:48]: the full commands printed out in yellow in the above log.
[13:47:48]: Make sure to inspect the output above, as usually you’ll find more error information there
[13:47:48]:
±--------------±---------------------+
| Lane Context |
±--------------±---------------------+
| PLATFORM_NAME | |
| LANE_NAME | build_for_inhouse_qa |
| BUILD_NUMBER | 3 |
±--------------±---------------------+
[13:47:48]: Error building the application - see the log above

±-----±------------------------------------±------------+
| fastlane summary |
±-----±------------------------------------±------------+
| Step | Action | Time (in s) |
±-----±------------------------------------±------------+
| 1 | Verifying required fastlane version | 0 |
| 2 | increment_build_number | 3 |
| :boom: | gym | 304 |
±-----±------------------------------------±------------+


#4

OK, there’s a path to your full log /Users/rajeshpanda/Project/banking-app-ios/fastlane/logs/NedBankApp-NedBankApp.log, so check that. Also, read the trouble-shooting docs it recommends. Good luck!


#5

Looks like a code signing error. You should make sure the provisioning profile is up to date. Are you using fastlane’s match tool?


#6

Yes the provisioning profiles are already there and it works fine with CircleCI 1.0
Unfortunately the same configuration is not working in CircleCI2.0.


#7

Is someone able to figure out the issue? It is working fine with circleci 1.0 but code signing fails with CircleCI 2.0 and XCode 9.2


#8

You’ll want to follow our 2.0 docs for it.
https://circleci.com/docs/2.0/ios-codesigning/


#9