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.
I had an email exchange about this issue with Adam Hartley on 2-15-2017 and 2-17-2017 under the subject "Quick Fix doesn't do anything". The problem is that right clicking in Xamarin Studio shows the Quick Fix menu item at the top of the popup menu but clicking that menu item doesn't show anything. Please see the attached videos for two examples. Adam had me uninstall Xamarin Studio on 2-15-2017 by running these commands in Terminal.
sudo rm -rf "/Applications/Xamarin Studio.app"
rm -rf ~/Library/Caches/XamarinStudio-*
rm -rf ~/Library/Preferences/XamarinStudio-*
rm -rf ~/Library/Logs/XamarinStudio-*
rm -rf ~/Library/XamarinStudio-*
After I ran these commands, the Quick Fix menu item worked as expected on 2-15-2017. However, this caused me to lose all of my Xamarin Studio preferences so I started setting them up again. I think the only things I changed were a few settings under Source Code --> C# Source Code --> C# Format --> Edit. On 2-17-2017 the Quick Fix menu item stopped working again and I've been testing it every once in a while to see if someone else reported the problem to you.
I think it was my C# source code settings that caused the Quick Fix menu item to break so if you tell me where those settings are stored I will send them to you to see if you can replicate the problem.
=== Xamarin Studio Community ===
Version 6.3 (build 864)
Installation UUID: babd5947-50bf-4615-a075-ff442f7fd352
Mono 220.127.116.11 (d15-3/14f2c81) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 502000224
=== NuGet ===
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Xamarin.Android ===
Version: 18.104.22.168 (Xamarin Studio Community)
Android SDK: /Users/gem/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.5
SDK Build Tools Version: 25.0.3
Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Android Designer EPL code available here:
=== Xamarin Inspector ===
Build date: Thu, 21 Sep 2017 19:52:53 GMT
Client compatibility: 1
=== Apple Developer Tools ===
Xcode 8.3.3 (12175.1)
=== Xamarin.iOS ===
Version: 22.214.171.124 (Xamarin Studio Community)
Build date: 2017-09-15 02:25:56-0400
=== Xamarin.Mac ===
Version: 126.96.36.199 (Xamarin Studio Community)
=== Build Information ===
Release ID: 603000864
Git revision: 6c2f6737278ccc3e81e12276d49c0d92f975f189
Build date: 2017-04-24 11:26:01-04
Xamarin addins: d8d46e577d8507c35260ce9d73df3c33415bb214
Build lane: monodevelop-lion-d15-1
=== Operating System ===
Mac OS X 10.12.6
Darwin iMac.local 16.7.0 Darwin Kernel Version 16.7.0
Thu Jun 15 17:36:27 PDT 2017
Created attachment 25008 [details]
Video of an Interface error
Created attachment 25009 [details]
Created attachment 25010 [details]
The C# Edit button that I clicked to change my preferences
That's a very detailed bug report :).
The version you're using is fairly old - it should work on a 7.x more reliable.
When I check for updates in Xamarin Studio Community it says that I'm up to date. When is 7.x scheduled to be released? I hope that this issue will actually be tested in 7.x rather than just expecting that it will work because you have improved the code in so many ways.