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.
A native library had only ARMv7 and i386 binaries and was build with MonoTouch's default (i.e. ARMv6) leading to a stackoverflow crash (on devices only) that took much time to diagnose.
Since [LinkAway] knows which architecture is available and `mtouch` knows what's the target architecture(s) we could issue a warning to say we'll be "ignoring" the native library. That hint would have saved quite a bit of time.
The new mtouch tool will issue warnings whenever a native library is ignored*, e.g.
warning MT1301: Native library `libATMHudSDK.a` (i386, ARMv6, ARMv7) was ignored since it does not match the current build architecture(s) (ARMv7+Thumb2)
or, inside MD's Error List like:
* it's not 100% accurate since it will warn if someone has libNormal.a, libSuper6.a, libExtra7.a and libAwesome7t.a for different architectures - but those warnings are much better than being blind to ignored libraries. We can revisit this if the new warnings becomes a too common problem.
Verified warning is present in 5.2.6