Bug 13339 - 'Renewal required to receive updates. Click to renew' on non-expired license
Summary: 'Renewal required to receive updates. Click to renew' on non-expired license
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- blocker
Target Milestone: ---
Assignee: Bo Pang
Depends on:
Reported: 2013-07-19 08:42 UTC by Mike James
Modified: 2016-08-03 15:25 UTC (History)
6 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 Mike James 2013-07-19 08:42:38 UTC
A customer is reporting that he is constantly being asked to activate his license. 

He is also being shown a label stating 'Renewal required to receive updates. Click to renew' when his license hasn't expired.
Comment 3 PJ 2013-07-23 10:17:38 UTC
He likely has an invalid license. Any way we can get the license file and/or entitlements output?
Comment 9 Dominique Louis 2013-07-31 08:18:56 UTC
OK looking at this now.
Comment 10 Dominique Louis 2013-08-12 12:08:17 UTC
This should have been fixed with Dean's Starter Edition fix. Are you still seeing this?
Comment 11 PJ 2013-08-12 12:13:03 UTC
I filed that one as 13451, and it's been fixed. I was going to leave this open for support to continue tracking some of the issues that might not be fixed by that fix.

That being said, it might be worth just closing this bug and seeing what new things are reported by support. Enough of these issues can be traced back to fixed issues that we need to start collecting more data.

I'll just do it, setting to RESOLVED FIXED.

Mike, Chris / support in general - it might be worth starting up a new bug for new activation issues and we'll see what can be categorized and fixed from the next crop. This one was a big help, but I'm not sure what else can be gleaned.