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.
Our Codesign task signs native libraries within and the while app bundle, but it does not sign bundled frameworks.
Conservatorio bundles the Sparkle app update framework, and has to extend MSBuild to codesign it :
<Target Name="CodesignSparkleFramework" BeforeTargets="_CodesignAppBundle">
<Exec Command="codesign -v --force --sign "$(CodeSigningKey)" "$(AppBundleDir)/Contents/Frameworks/Sparkle.framework"" />
This is suboptimal for two reasons:
1. this should be handled automatically
2. it depends on _CodesignAppBundle, which is considered a 'private' API due to the _ prefix, so future XM releases may break it
XI codesigns frameworks now, so maybe this logic can be shared somehow.
XI supports embedding frameworks using the same logic as for binding projects, so this should be trivial to implement (and share implementation too).
This should be fixed with LinkWith support (now in master). You still have to hack your binding project to copy in the framework, but that is the same for XI right now.