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 MonoTouch the installer has a page where it offers you different ways to install. The only option available is 'Install for all users of this machine'. This option is automatically selected for you. However the 'Continue' button on that page is not enabled even though the option is selected. You have to click on it again before you can click 'Continue'.
It's a confusing experience. Can we improve this?
Observed that the above mentioned screen appear only when the machine has more than one User.
Also, there is no option to Install Xamarin.iOS for the current user only.
First screen is from a machine with more than one user .
Second screen is from a machine with only one user.
Yeah this is definitely not grendel.
I don't think anything has changed here, but if we want to investigate further http://stackoverflow.com/questions/11487596/making-os-x-installer-packages-like-a-pro-xcode4-developer-id-mountain-lion-re is a decent read.
There has not been changes to the package recently so I believe it's been like this since (at least) Xamarin 2.0 times (when we dropped -eval and switched format for the main one) or maybe forever.
A quick googling shows that this same (weird) behaviour happens in several packages. That sounds like an Apple bug. I did not see workaround (just end-users noticing it) but maybe there's one (I have not read thru PJ's link yet).
Also, like Gouri mentioned, the fact that most computers are single user system means it's not an issue that many people will see. IMO multi-users system users, with admin rights to install packages, are less likely to be confused by this.
note: if someone has time to check 3rd party packages to see if they all behave the same… that will give us a clue if there's a workaround (or not);
This seems to be working as intended, especially based on comment 1. RESOLVING as UPSTREAM due to this being the way the installer tool works.