Bug 61104 - "Xamarin licence file is invalid" on every VS launch and first build
Summary: "Xamarin licence file is invalid" on every VS launch and first build
Status: RESOLVED ANSWERED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Activation ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-12-15 08:21 UTC by kontakt
Modified: 2017-12-27 08:11 UTC (History)
6 users (show)

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


Attachments
The dialog (10.55 KB, image/png)
2017-12-15 08:21 UTC, kontakt
Details


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:
Status:
RESOLVED ANSWERED

Description kontakt 2017-12-15 08:21:03 UTC
Created attachment 26012 [details]
The dialog

Everytime I launch Visual Studio and do the first build, I got this dialog:
"The Xamarin license vile is invalid and could not be recovered."
"You will still be able to access the Xamarin features that are included in Visual Studio Community."
"Use Visual Studio Community" button

Then I need to click the button, build is cancelled. Now I need to run the build again and it is ok.
But it's pretty annoying, because usually I need to restart the VS few times a day because of some other bugs. Sometimes I just start the build and go get a coffee and when I return I found out that this just happend and the app did not build and I need to wait for the build again. OMG!

It is only happening since the last time I updated VS, which is about a week or two ago.

My VS system info:
Microsoft Visual Studio Community 2017 
Version 15.5.0
VisualStudio.15.Release/15.5.0+27130.0
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Community

Visual Basic 2017   00369-60000-00001-AA614
Microsoft Visual Basic 2017

Visual C# 2017   00369-60000-00001-AA614
Microsoft Visual C# 2017

Visual F# 4.1   00369-60000-00001-AA614
Microsoft Visual F# 4.1

Application Insights Tools for Visual Studio Package   8.10.01106.1
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2017   15.0.31120.0
ASP.NET and Web Tools 2017

ASP.NET Core Razor Language Services   1.0
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2017   5.2.51007.0
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   15.0.31106.0
Azure App Service Tools v3.0.0

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service   2.0
JavaScript Language Service

JavaScript Project System   2.0
JavaScript Project System

Merq   1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 2017 - v2.9.51120.3

Microsoft Continuous Delivery Tools for Visual Studio   0.3
Simplifying the configuration of continuous build integration and continuous build delivery from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual Studio Tools for Containers   1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

Mono Debugging for Visual Studio   4.8.4-pre (3fe64e3)
Support for debugging Mono processes with Visual Studio.

Node.js Tools   1.4.11025.7
Adds support for developing and debugging Node.js apps in Visual Studio

NuGet Package Manager   4.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

SQL Server Data Tools   15.1.61710.120
Microsoft SQL Server Data Tools

TypeScript Tools   15.5.11025.1
TypeScript Tools for Microsoft Visual Studio

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

Xamarin   4.8.0.752 (4a1f0ea)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   4.8.182 (76aa1723e)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin.Android SDK   8.1.0.24 (HEAD/9cfa7836b)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK   11.4.0.214 (c4240f3)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Comment 1 Daniel Vaughan 2017-12-15 11:16:24 UTC
I've experienced the same issue since Visual Studio 15.5.1
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2017-12-16 03:10:24 UTC
Thanks for the report!  This issue appears to match https://developercommunity.visualstudio.com/content/problem/130418/xamarin-license-detector.html.  We recommend that you vote on and follow that issue on Developer Community for updates and fix notifications.

I will mark this Bugzilla item as "RESOLVED" to consolidate updates onto that matching Developer Community item.
Comment 3 softlion 2017-12-27 08:11:18 UTC
So the workaround is to delete the file %APPDATA%\VisualStudio\account.json