Bug 6496 - MFA does not appear in MD info tab after updating, causing MFA projects to fail to load
Summary: MFA does not appear in MD info tab after updating, causing MFA projects to fa...
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.2.x
Hardware: Macintosh Windows
: High critical
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2012-08-09 16:15 UTC by Peter Collins
Modified: 2012-08-29 06:31 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Peter Collins 2012-08-09 16:15:18 UTC
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.

Expected Behavior:
Updating MD and MFA through the MD updater will close, update, and restart MD. All updates will complete and be recognized.

Actual Behavior:
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.

Environment Details:
Win7 32bit AND win7 64bit VMs run on VMWare, Host: OSX Lion 10.7.4

Updating from:
MD 3.0.3.5
MFA 4.2.4.167234518 (Evaluation)

Updating to: 
MD 3.0.4.3
MFA 4.2.5.195540401

Gist for list of processes under MonoDevelop.exe:
https://gist.github.com/3307356
Comment 1 Mikayla Hutchinson [MSFT] 2012-08-09 17:02:15 UTC
If this is only on a fresh install, might it have something to do with the addin engine?
Comment 2 Peter Collins 2012-08-13 16:34:21 UTC
Just ran into this same issue again on a win8 x32 VM, however closing MD 3.0.4.3 and restarting it did not resolve the issue. After rolling back to the stable MD 3.0.3.5, my version of MD recognized MFA. However, once I then installed MD 3.0.4.3 from the alpha channel, MFA was once again unrecognizable.
Comment 3 PJ 2012-08-16 14:18:56 UTC
Let's get this reproduced on a physical machine. Once we're in the state - what can we get you mhutch?
Comment 4 Mikayla Hutchinson [MSFT] 2012-08-16 14:37:57 UTC
I don't know, we really need to get lluis to look at this.
Comment 5 Peter Collins 2012-08-16 18:24:23 UTC
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 3.0.4.3 through the MD updater.*

Installing MFA alpha first (without the updater) and then using the updater to update MD from 3.0.3.5 to 3.0.4.3 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.
Comment 6 PJ 2012-08-16 18:41:31 UTC
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.
Comment 7 Mikayla Hutchinson [MSFT] 2012-08-16 18:53:42 UTC
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?
Comment 8 Lluis Sanchez 2012-08-29 06:31:33 UTC
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.