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 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.
If a user has an old expired trial license in %LOCALAPPDATA%\VirtualStore\ProgramData, then no amount of logging-out, logging-in, re-installing, or deleting %PROGRAMDATA%\Mono*\License will stop these two errors:
> Trial period has expired. (XA9001)
> Unable to determine license edition. (XA9010)
1. Log out of your Xamarin account from Xamarin Studio or Visual Studio.
2. Quit Xamarin Studio and Visual Studio.
3. Delete the %LOCALAPPDATA%\VirtualStore\ProgramData\Mono*\License folders
4. Delete the %PROGRAMDATA%\Mono*\License folders
5. Open Xamarin Studio or Visual Studio, and log back into your Xamarin account.
Note: completing just steps 2 and 3 might be sufficient.
## Potential enhancements
a) The new license-sync mechanism could be updated to check for the %LOCALAPPDATA%\VirtualStore\ProgramData\Mono*\License folders, and clear them out whenever clearing the %PROGRAMDATA%\Mono*\License folders.
b) Xamarin.Android and XamarinVS.iOS could be updated so they only ever look in %PROGRAMDATA%\Mono*\License for license information. Depending on how Windows handles the special VirtualStore folder, this might or might not be possible.
c) Maybe the code that created the `VirtualStore` version of the license has already been removed. In that case, since this problem seems to be quite rare, it might be sufficient just to have this bug report available. That way, at least anyone who hits the problem in the future will be able to find the workaround more easily.
*** This bug has been marked as a duplicate of bug 21284 ***