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.
I have Xamarin.Android 188.8.131.52 installed as indicated by:
1. the .pkg installer that installed it (xamarin.android-7.4.0-15.pkg)
2. the tupling of /Library/Frameworks/Xamarin.Android.framework/Versions/Current/Version and /Library/Frameworks/Xamarin.Android.framework/Versions/Current/Version.rev
3. /Library/Frameworks/Xamarin.Android.framework/Versions/Current/Version.commit further indicates: HEAD/a93c6f4
However, the version specified in [assembly: AssemblyInformationalVersionAttribute] for Mono.Android.dll does not match. It is instead "184.108.40.206; git-rev-head:edf9ac5; git-branch:d15-3"
Both the version and the commit differ.
I would expect everything to be in sync, otherwise the assembly itself cannot be used to track back to the actual release of the product.
Looks to be related to bug #57725.
I can CONFIRM this behavior based on the observations in https://bugzilla.xamarin.com/show_bug.cgi?id=58396#c0
I am also running 220.127.116.11 and I'm seeing the following in the v7.1 Mono.Android.dll:
[assembly: AssemblyInformationalVersion("18.104.22.168; git-rev-head:57ba08b; git-branch:d15-3")]
Version - 7.4.0
Version.commit - HEAD/a93c6f4
Version.rev - 15
*** This bug has been marked as a duplicate of bug 57725 ***