Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Apple introduced a bug with the codesign tool in OS X 10.9.5 that is mentioned in: http://stackoverflow.com/questions/26008449/xcodebuild-codesign-vvvv-saysresource-envelope-is-obsolete
Codesign fails for some configurations with the message: "resource envelope is obsolete (custom omit rules)."
There is a workaround: "The command line tool “codesign” has changed in 10.9.5 and 10.10, you need to pass “--no-strict” option to the command, (the problem has been reported and will be fixed)."
Xamarin could work around the Apple bug with the following code change to Xamarin.iOS.Tasks.Core.dll:
public abstract class CodesignVerifyTaskBase : Xamarin.MacDev.Tasks.CodesignVerifyTaskBase
protected override string GenerateCommandLineCommands()
ProcessArgumentBuilder processArgumentBuilder = new ProcessArgumentBuilder();
processArgumentBuilder.Add( "--verify" );
new --> processArgumentBuilder.Add( "--no-strict" );
processArgumentBuilder.Add( "-vvvv" );
processArgumentBuilder.Add( "-R='anchor apple generic and certificate 1[field.1.2.840.113622.214.171.124.1] exists and (certificate leaf[field.1.2.840.1136126.96.36.199.2] exists or certificate leaf[field.1.2.840.1136188.8.131.52.4] exists)'" );
processArgumentBuilder.AddQuoted( this.Resource );
Note the addition of the no-strict parameter. I tested this parameter and found it to work around the Apple bug for my projects.
From what I can see Apple's bug is already fixed in the latest versions of OS X 10.10, and our next version of Xamarin.iOS will require Xcode 7, which requires OS X 10.10, so as far as I can tell we don't need to work around Apple's bug (since the next version of Xamarin.iOS won't work on 10.9 anyway).
This codesign misbehavior is occurring with OS X 10.10 and XCode 7. I discovered the problem yesterday after upgrading both. I also tested the work around and found that it resolves the failure.
Correction: I upgraded to OS X El Capitan which is 10.11 -- not 10.10.
Check your Info.plist for a CFResourceRules (I think?) key. If it exists, then that is the problem.
I recently made a fix related to this.
Oops, the Info.plist key is CFBundleResourceSpecification
*** Bug 34845 has been marked as a duplicate of this bug. ***
The problem is that the iOS SDK you're using uses custom resource rules when signing, which are no longer supported on OS X 10.9.5 and later.
Removing the custom resource rules should fix the codesign issue.
With the cycle6 release published today, this should no longer be a problem since we no longer specify ResourceRules.