Bug 37714 - error MT9000: This version was released after your subscription expired
Summary: error MT9000: This version was released after your subscription expired
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 9.4 (iOS 9.2)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-01-15 04:55 UTC by Prashant Cholachagudda
Modified: 2016-01-15 19:37 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 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:

Description Prashant Cholachagudda 2016-01-15 04:55:52 UTC
One of the customers is getting the `MTOUCH: error MT9000: This version was released after your subscription expired (07/12/2015 21:14:25)` even when license is valid and active 

## Version Information

=== Xamarin Studio ===

Version 5.10.1 (build 6)
Installation UUID: 6373733c-9fc3-400b-ae6c-3c6b8dabc2b1
Mono 4.2.1 (explicit/6dd2d0d)
GTK+ 2.24.23 (Raleigh theme)

Package version: 402010102

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 7322991
Branch: master
Build date: 2015-12-08 16:20:29-0500

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/Shared/SDKs/android-sdk-macosx
Supported Android versions:
2.3 (API level 10)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.2

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Not Installed

=== Xamarin.Mac ===

Not Installed

=== Build Information ===

Release ID: 510010006
Git revision: 0b60eecdb531933734519c13257d16a780274aab
Build date: 2015-12-04 20:28:20-05
Xamarin addins: 9876fd7c9837977178411ec7375b4352c0a0d6af
Build lane: monodevelop-lion-cycle6-baseline

=== Operating System ===

Mac OS X 10.11.2
Darwin Martins-Mac-mini.local 15.2.0 Darwin Kernel Version 15.2.0
Fri Nov 13 19:56:56 PST 2015
root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64
Comment 2 Rolf Bjarne Kvinge [MSFT] 2016-01-15 10:08:13 UTC
This seems to be happening when using an automated build.

Those are often executed using a different user, which must also have a valid license.

Please get the following data *from the automated build* (not executing it in a terminal):

    /Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch --entitlements
Comment 3 Martin Evans 2016-01-15 13:09:46 UTC
Hi. "I'm the customer" and here's a bit of background to the case:

This issue occurred when building the project via a Jenkins build project on my Mac. I also connect to this same Mac via the Xamarin Mac Agent from my windows machine to build from Visual Studio and the build completes successfully.

Hope this info helps.

Comment 4 Rolf Bjarne Kvinge [MSFT] 2016-01-15 15:42:21 UTC
@Martin, can you do what I ask for in comment #2?
Comment 5 Martin Evans 2016-01-15 17:23:45 UTC
Version :  9.2.1
	Automated Build
		ac84b1788e054b3d17c0af9213656d4217563c6f MonoTouch Business 2015-12-07T21:14:25
	Command Line
		a4c59cd22f048c10dee140767a2ef1111d6bacbd MonoTouch Business 2016-12-07T21:14:25
Version :
	Automated Build
		ac84b1788e054b3d17c0af9213656d4217563c6f MonoTouch Business 2015-12-07T21:14:25
		error MT9000: This version was released after your subscription expired (07/12/2015 21:14:25).
	Command Line
		a4c59cd22f048c10dee140767a2ef1111d6bacbd MonoTouch Business 2016-12-07T21:14:25
Comment 6 Rolf Bjarne Kvinge [MSFT] 2016-01-15 18:07:02 UTC
The date is different between the automated build and the command line. This means you're using a different user account for the automated build. You need to run Xamarin Studio and log in in all user accounts you're using to build.
Comment 7 Martin Evans 2016-01-15 18:12:49 UTC
Hi Rolf,

you saw the results from running the test in 9.2.1 and I ran the first tests then simply updated xamarin.ios to and re-ran the tests and the issue occurred.

Why would I be expected to do anything different to use

Has introduced a feature that requires me to change how I use my build server or is it some undocumented/unexpected behavior that's causing this?

Comment 8 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-15 18:19:08 UTC
9.2.1 was published on December 1, 2015, before December 7, 2015, so your old un-renewed license that's being used by the automated build user account accepts that version.

Version 9.4.0 was published more recently (December 9, 2015), so it's hitting the account expiration date.

To reiterate comment 6 in case it might help further clarify, the fix for this issue is simply to refresh your license in the user account on the Mac that is used for the automated builds.
Comment 9 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-15 18:21:09 UTC
(See also: https://kb.xamarin.com/customer/portal/articles/1641743-manually-resynchronize-xamarin-licenses)
Comment 10 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-15 18:21:42 UTC
(The "Quick manual refresh steps" should be sufficient in this case.)
Comment 11 Martin Evans 2016-01-15 19:37:45 UTC
Thanks all. 

Working now.

Keep up the good work. :-)