Jenkins vs. Xcode plugin - codesign troubles

Question

I have updated to OS X Yosemite and also Xcode 6.1 (downloaded from the developer site), from this time I have had the problem with the building as in the log file I see the

Answer 1

The answer provided by Julius Lisauskas will resolve the warning, but it is actually just a workaround for a bug that exists in the Jenkins Xcode plugin xcrun.

As mentioned in Apple Technical Note TN2206:

Systems before OS X Mavericks documented a signing feature (--resource-rules) to control which files in a bundle should be sealed by a code signature. This feature has been obsoleted for Mavericks. Code signatures made in Mavericks and later always seal all files in a bundle; there is no need to specify this explicitly any more. This also means that the Code Signing Resource Rules Path build setting in Xcode should no longer be used and should be left blank.

It is thus no longer possible to exclude parts of a bundle from the signature. Bundles should be treated as read-only once they have been signed.

There is an issue raised on the Jenkins Xcode plugin regarding this bug that concludes the bug lies in Xcrun.

Answer 2

As specified in another answer, you can also just not specify the distribution certificate to sign with and it will package correctly.

Answer 3

Everything is ok with Jenkins plugin. Just product settings is incorrect.

Open the "Build Settings" tab of your project. Searched "Code Signing Resource Rules Path", it was empty for me. Change to: $(SDKROOT)/ResourceRules.plist

credits goes to Adams Blair who described this problem with SDK2.2

https://stackoverflow.com/a/7919137/2124345

Update

This solution doesn't remove the warning itself. But i'm pretty sure that warning isn't a problem. The problem is that without this setting ResourceRules.plist files isn't generated in Payload folder, and build process stops because file is missing.

And again, it's not related with jenkins plugin at all. Same error happens with xcrun -sdk iphoneos PackageApplication. Jenkins just calling this command line as a build step.