Bug 10849 - Can't login to Xamarin account
Summary: Can't login to Xamarin account
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Activation ()
Version: 1.0.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Dominique Louis
Depends on:
Reported: 2013-03-03 10:49 UTC by Neal
Modified: 2013-06-03 13:53 UTC (History)
2 users (show)

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 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:

Description Neal 2013-03-03 10:49:36 UTC
I posted this to the forums by mistake, I'm confused what to post where (e-mail, forums, bugzilla)!!  So as I think this is a bug I'll report it here.

VS 2012 under Win8 Pro x64 - Xam 2.0 installed, using Android

Under Tools menu there is the Xamarin account.  I can't sign in and not sure what doing so does.

This computer had MfA previously installed and activated if that helps troubleshoot the issue
Comment 1 Dominique Louis 2013-06-03 13:51:14 UTC
Hi Neal,
  Could you please provide us with more detailed information on how to reproduce this bug. FYI you should be logged into your Xamarin Account, so that the licence activates correctly.

Comment 2 Neal 2013-06-03 13:53:56 UTC
It works now, may have been a glitch at the time.