I am little concerned about how people treat the following issue.
Basically it sounds like "Build fails on Jenkins with the ResourceRules.plist: cannot read resources
"
My circumstances are:
1) Jenkins
2) Locally I work in Xcode 7 beta (on a separate branch)
3) My teammates work in 6.4.1 and for them everything works fine
4) Jenkins slave has Xcode 6.4.1 installed
Some of you will say "this question was asked millions of times", like here, here, here, here.
But the documentation says the following:
Resource Rules
Systems before OS X Mavericks v10.9 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.
So my question is why everybody is so quick on hand to bypass, hack, workaround this issue, when the documentation clearly says that is should be blank and it's obsolete?
What is the real problem behind this? Why the build fails on something that is not required for several years?