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.
This issue is seemingly difficult to reproduce, however I have been able to consistently reproduce this issue on a win7 VM snapshot of a fresh MD and MFA install. I have gone back and forth from the current stable channel to the alpha and have also been able to reproduce, it doesn't require restoring the snapshot of the fresh install.
Updating MD and MFA through the MD updater will close, update, and restart MD. All updates will complete and be recognized.
After updating MD and MFA from the alpha channel, MD restarts but does not recognize that MFA is installed. Closing and restarting MD after this issue occurs causes MD to recognize the updated MFA.
Win7 32bit AND win7 64bit VMs run on VMWare, Host: OSX Lion 10.7.4
MFA 22.214.171.124234518 (Evaluation)
Gist for list of processes under MonoDevelop.exe:
If this is only on a fresh install, might it have something to do with the addin engine?
Just ran into this same issue again on a win8 x32 VM, however closing MD 126.96.36.199 and restarting it did not resolve the issue. After rolling back to the stable MD 188.8.131.52, my version of MD recognized MFA. However, once I then installed MD 184.108.40.206 from the alpha channel, MFA was once again unrecognizable.
Let's get this reproduced on a physical machine. Once we're in the state - what can we get you mhutch?
I don't know, we really need to get lluis to look at this.
Repro'd again on a physical win7x64 machine, closing MD and reopening causes MD to recognize that MFA exists.
*The bug is reproducible when only updating MonoDevelop to 220.127.116.11 through the MD updater.*
Installing MFA alpha first (without the updater) and then using the updater to update MD from 18.104.22.168 to 22.214.171.124 causes this issue consistently. However, updating MD alpha first (without the updater) and then using the updater to update MFA from 4.2.4 to 4.2.5 does not cause this issue.
Another thing to note is that issue seems to be specific to Windows. I have been unable to repro on OSX Lion and Mountain Lion, while I have consistently been able to repro this issue on Win7 and Win8 32 and 64bit versions.
Assigning to Lluis as per comment 4.
He's on FTO till the end of next week. Do we want to procede with this release before then? I'd imagine there would be a huge influx of support case about it if we did.
CC'ing chrisntr to weigh in on the support implications.
Is it specific to this version, or just specific to updating?
Is there anything in the MD log file from the MD session in which this bug occurs?
A fix has been committed to master and 3.0.4 branch. It is a fix in the updater, so the fix can only be verified with an MD version that includes the new updater being updated to a different version.