All geek questions in one place

Running iPhone Xcode Tests with Cruise Control

When using Cruise Control to create an iPhone Xcode project using Unit Tests, the error "Code sign error: generates a valid provisioning profile that matches the application identifier" com.yourcompany.Calculator "that was not found." Does this not occur when passing through Xcode? Is cruise control trying to run the application, not just build it? Any suggestions?

+4
source share
2 answers

The problem was caused by the addition of the Unit Test package to the project. To ensure that the tests were built and run with the main project, I dragged the unit test target group to the main goal project. By default, he assigned the Unit Test kit, which will be created against the iPhone Device 3.1.2 SDK, not the simulator. In addition, a unit-generated .plist file was created in the Unit Test package containing the default Bundle identifier for com.yourcompany ... etc. Therefore, despite indicating the target, which, as I knew, had a default SDK for iPhone Simulator 3.1.2, the inclusion of the Unit Test package led to the fact that the error continued to appear. Selecting Get Info for Unit Test, select the Build tab and install the base SDK on iPhone Simulator 3.1.2, and everything will be fine.

0
source

I do not know for sure if xcodebuild starts the code signing tool correctly, but it seems to me that you will need to change the build process to use this tool ( codesign ).

I'm not sure if this is a pre-build or post-build task.

codesign man page: http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man1/codesign.1.html

According to this SO post, you can get around this by telling xcodebuild assume that the target is iPhone Simulator instead of the real iPhone (with the -target command line option)

+2
source

Source: https://habr.com/ru/post/1300208/

More articles:


All Articles