Bug 1613 - Monodroid Reactivation Required on Reboot
Summary: Monodroid Reactivation Required on Reboot
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 1.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-10-20 11:25 UTC by Chris Schamper
Modified: 2012-03-23 16:25 UTC (History)
6 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 Chris Schamper 2011-10-20 11:25:14 UTC
Monodroid in Monodevelop reverts to demo mode upon reboot. Activation code no longer activates product.
Comment 1 dellis1972 2011-11-09 14:20:50 UTC
I have the same issue. After a reboot the activation of Mono Android is no longer valid and I have to reactivate the product. 

This is under monodeveloper 2.8.2
Comment 2 Chris Schamper 2011-11-17 17:09:01 UTC
In my case, this was caused by a soft NIC's MAC address resetting on each reboot.

A change in a NIC's MAC address caused the validation to reset.
Comment 3 Jonathan Pryor 2011-11-17 17:43:26 UTC
We think we've mitigated this in 2.0. Please let us know if it continues to persist after the 2.0 release.
Comment 4 Jonathan Pobst 2012-03-23 16:25:17 UTC
No response, this should be fixed.

If you still experience this, please reopen!