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.
(All in a VS2017RC installation:)
Found: An inability to click through a "Xamarin Updates Available" notification.
Found: No "Other" category under Tools -> Options -> Xamarin.
The consequence is that the notification triggers each
and every time I launch VS2017 and open a solution
containing Xamarin.iOS or Xamarin.Android projects.
Furthermore, the absence of an "other" settings
category (I only have iOS, Android settings now visible)
means channel selection/updates are apparently now
inaccessible from the IDE.
* I have used the 2017RC installer to uninstall the entire
product and reinstall to no effect.
* Is there some dirty registry use in play here that
survives an uninstall/reinstall cycle?
Any insight in how to recover update capability is
appreciated. Many thanks.
Having the same problem in VS2017RC. Currently running 4.3.598 and cannot update.
Hi Brian, Ron,
Starting VS 2017 Xamarin will update through VS own updating mechanism. That's the reason why you have noticed the option to update Xamarin is gone from VS now. When there is a new Xamarin build compatible with VS 2017 you will see a notification inside VS that will let you upgrade. Also, every time you update from one VS 2017 RC to the next one, you are most probably getting a newer Xamarin build too.
There is still a bug, which is causing the update pop up to appear, which we will fix soon (before VS 2017 RTW).
Thanks for the additional info.
How will alpha/beta/stable channel selection work under the VS2017 update mechanism? Just curious.
I'm currently running version 4.3.598 and I see there are 188.8.131.529 and a .621 releases on the website. Are these newer releases not compatible with VS 2017, or should I expect the Xamarin extension to update?
*** Bug 52363 has been marked as a duplicate of this bug. ***
@Ron, if you update to VS 2017 RC.4 you will get a newer build of Xamarin. If you are running VS 2017 RC.3 you should get a notification in VS that says there is a newer VS build, that will bring a newer Xamarin build with it.
@Brian, some details are still being worked out. For VS 2017 you will install VS 2017 itself from different "channels" (note this selection happens at installation time, using the Willow UI) and then that VS instance will keep installing newer Xamarin builds from that channel.
The pending fix on Xamarin side before being able to resolve this bug is to completely remove the Xamarin Updater from VS, which right now has been disabled, but still keeps popping up with notifications that are not applicable to VS 2017.
The notification pop up was removed already in the latest VS2017 RC4. (Xamarin 184.108.40.2064)
@Jose still getting this issue on 220.127.116.114 so it would seem that is not the case.
Couple of questions:
1. Do you have only VS2017 installed? Or do you have another VS version with Xamarin as well? (which can be triggering the pop-up)
2. How did you get 18.104.22.1684? Did you uninstall the previous VS 2017 and installed the latest one or did you just update it? Because there is an issue updating to RC4 that ends up with both the new and the previous extension running at the same time, which can make the old extension to show the notification, even if 664 is installed.
Please provide the requested info. That said, we'll check once again just in case there is another scenario where 664 is still getting the notification.