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.
Created attachment 6998 [details]
Not sure how to fix this one...
You should contact Avast, it's their heuristics.
Does it just happen with that app or all Xamarin.iOS apps?
Ian, Sadly there's nothing we can do on our end.
The best thing you can do is (like Michael said) contact Avast and provide them with the binary and a description of the problem, like:
"Somehow your software see a pattern inside an ARM executable, which is not something the Mac itself can execute. I'm not sure why it's even being scanned ?"