Bug 14381 - VS Tells me to reactivate my Mac server
Summary: VS Tells me to reactivate my Mac server
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.6.x
Hardware: PC Mac OS
: High major
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2013-09-02 21:33 UTC by James Clancey
Modified: 2013-09-11 08:31 UTC (History)
4 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 James Clancey 2013-09-02 21:33:49 UTC
At least every other day, if not once a day, VS tells me that I have to reactivate my mac server.  I click reactivate, and it says it activated on my mac. But the dialog never updates. Every time I click reactivate on my windows machine you see the dialog on the mac server.

The activation does not seem to stick until I restart VS. 

If my server was a headless mac instead of a laptop sitting next to my workstation it would be very very painful to have to log into the mac to see whats going on.
Comment 1 James Clancey 2013-09-03 17:17:59 UTC
If I click cancel on the activate server dialog, then restart VS. I never have to go through the activate process.
Comment 2 dean.ellis 2013-09-11 08:31:36 UTC
This was a bug in the GetServerInfo returning invalid data, the server was actually activated but because the call to touch --list failed the call failed. 

This has now been reworked and activation is now fixed