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.
Xamarin.android won't build after upgrading to El Capitan. The problem is caused by the SIP change where non-system links aren't allowed in /usr/bin which is where mono installs them. Mono doesn't actually need them but the Xamarin.Android tools reference them without a path, causing failures.
I specifically fixed a line in the /Library/Frameworks/Xamarin.Android.framework/Commands/generator script. It had:
exec mono $MONO_OPTIONS "$MANDROID_DIR/generator.exe" "$@"
This would get an error that it couldn't find 'mono'. Changing the line to this worked:
exec /Library/Frameworks/Mono.Framework/Commands/mono $MONO_OPTIONS "$MANDROID_DIR/generator.exe" "$@"
I'm sure there are other scripts Xamarin.Android tools that will fail for similar reasons. The above fix should probably be getting the path via an enviroment variable so it uses the selected mono runtime set in xamarin studio.
FIxed in monodroid/5cae13fd and monodroid/cycle6/418c64df.
This should be present in the most recent cycle6 Alpha.