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 20008 [details]
Please find the Verbose Log.
Created attachment 20014 [details]
Updated Verbose Log
Attaching updated verbose log.
I tried to reproduce this on two different machines and had no problems. Whatever this issue is here I guess it must be environment related.
Microsoft Visual Studio Enterprise 2017
Version 15.0.26226.0 D15REL
Microsoft .NET Framework
Xamarin 184.108.40.2064 (73f58d6)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 220.127.116.11 (9578cdc)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.4.0.Java JDK 1.8.0_112123 (35d1ccd)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Can you attach the diagnostics level of the build output (Tools > Options > Projects and Solutions > Build and Run > MSBuild project build output verbosity) when compiling the project after you have added the button?