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 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.
Currently, the first build of an Android app in VS can take upwards of ten minutes, as various Android libs are downloaded and extracted. There is no notification to the user as to current status or other aspects, it just takes a long time. Many will simply cancel the build and think something is broken.
I believe there are some efforts to either reduce or eliminate these delays, but in the mean time, are we able to provide the user with a notice that the build will take a long time?
This is not the expected behaviour, basically we are detecting the required additional resources to download and an error is added to ErrorList in order to give the complete list of components to install to user, when user clicks on the error a progress dialog is opened, it gives feedback of download/unzip to user.
Can you please add the following information?
1. Information or solution sample to reproduce it. What kind of android project is? has nuget packages?
2. Xamarin Logs
Go to the menu "Help - Xamarin - Zip Logs". Please attach that zip file to the bug report.
3. Environment information
Go to the menu "Help - About Microsoft Visual Studio" and press "Copy Info". Please paste that info into a Bugzilla comment.
4. Diagnostic Build Output
Go to the menu "Tools - Options" and from the left panel: "Projects And Solutions - Build And Run" and change "MSBuild Output Verbosity" to "Diagnostic", and then build the solution. Copy the Build Output from the Output window and share it (maybe in a gist or as a zip file).
As we've introduced several improvements around this area, I'll mark the bug as resolved fixed.
Please feel free to reopen it if you can still reproduce the issue with current bits.