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.
When installing products, the updater has a progress bar that indicates the number of things installed.
So if you are done with one installation out of two, for example, it sits at 0% during the whole first product's installation, then sits at 50% during the second product's installation. For a while I thought the updater was freezing with this behavior.
Which leads to this experience: http://screencast.com/t/G7REFl6HUSq
:00-2:31 - progress bar is blank, saying Installing Mono for Android
2:32-2:33 - progress bar moves from empty to halfway
2:34-2:48 - progress bar is halfway, Monodevelop is installing
2:49 - updater disappears.
More granular progress indication.
Clearly an enhancement/feature request - filing as such.
Technically the updater does support granular progress reporting for pkg and app installation, unfortunately it falls back to the observed behaviour for two reasons. Firstly, the Mono for Android installer has to run externally so that it can display activation UI, and that means it doesn't report progress directly. Secondly, if the app bundle is in a location owned by root, we install it with an escalated cp command, which also doesn't report progress.
It might be possible to fix the first case by reading status messages from system logs, and fix the second case by using some other copying mechanism.
This is a bug in the MfA and MonoTouch packages, IMO.
As part of Xamarin 2.0, the XA/XI packages were fixed not to require an interactive install.