Unhandled Activation Error (repeated, account is on subscription)

XS just started (today sometime) a cycle of asking me to log in, showing a valid license status, then popping an "Unhandled Activation Error" dialog with:

System.InvalidOperationException: Sequence contains no matching element
at System.Linq.Enumerable.First[LicenseSyncResult] (IEnumerable1 source, System.Func2 predicate, Fallback fallback) [0x00050] in /Volumes/build-root-ramdisk/mono-3.6.0/mcs/class/System.Core/System.Linq/Enumerable.cs:830
at System.Linq.Enumerable.First[LicenseSyncResult] (IEnumerable1 source, System.Func2 predicate) [0x00007] in /Volumes/build-root-ramdisk/mono-3.6.0/mcs/class/System.Core/System.Linq/Enumerable.cs:855
at Xamarin.Components.Ide.Activation.ActivationExpiredWorkflow.Start (XamarinProduct product, Xamarin.Components.Ide.Activation.LicenseSyncResult[] results) [0x00043] in /Users/builder/data/lanes/1063/e797f287/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationExpiredWorkflow.cs:31
at Xamarin.Components.Ide.Activation.ActivationService+c__Iterator1+c__AnonStorey7.<>m__0 (Xamarin.Components.Ide.Activation.LicenseSyncResult[] r) [0x0000c] in /Users/builder/data/lanes/1063/e797f287/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:107
at Xamarin.Components.Ide.Activation.ActivationService+c__Iterator4.MoveNext () [0x004ca] in /Users/builder/data/lanes/1063/e797f287/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationService.cs:617
at Xamarin.Components.Ide.Activation.ActivationDialog.DisplayWorkflowStep (Xamarin.Components.Ide.Activation.ActivationWorkflowStep step) [0x0002c] in /Users/builder/data/lanes/1063/e797f287/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationDialog.cs:455
at Xamarin.Components.Ide.Activation.ActivationDialog+c__AnonStorey4.<>m__0 (System.Threading.Tasks.Task t) [0x0005b] in /Users/builder/data/lanes/1063/e797f287/source/md-addins/Xamarin.Ide/Xamarin.Components.Ide/Activation/ActivationDialog.cs:553

This experience repeats, denying use of features (along with the constant annoyance).

Is anyone else seeing this? (Known activation service issues?) (Other?)

Thanks!

Posts

  • plynkusplynkus USMember

    ...after a bit of searching, this appears to be resolved.

    The issue is that XS (and the associated license/activation elements) got unspooled by the condition where:

    (1) A valid subscription exists online.
    (2) An expired license still exists (~/Library/Xamarin.Mac/License).

    The key piece of info (not apparent at first) came when attempting different build/clean patterns to extract some more info before getting locked into the IDE's activation cycle.

    "Error MM9000: This version was released after your subscription expired (7/6/2014 5:14:19 AM). (MM9000)"

    It would seem that some parts of the IDE are taking the local license as authoritative, while others are invoking the login/activation flow that should resolve activation as a result. Though I do see a positive response (an indie subscription confirmation dialog), nothing was done to either update or purge this license file---perhaps related to the exception I noted earlier. In any case, the toolchain was never made happy and the cycle repeated over and over.

    The solution (though this shouldn't be required) was to download a new license file manually and shove it in the location mentioned above.

    Here's hoping that the toolchain activation flow gets a little more robust by next year, when I will have likely forgotten all of this. :)

  • mhutchmhutch USMember, Xamarin Team Xamurai

    Yes, we're in the process of updating Xamarin.Mac to use the IDE activation system that Xamarin.Android and Xamarin.iOS use, and some of the changes were accidentallyreleased prematurely. Specifically, if the mmp tool outputs an activation error code it's now passed to the IDE activation system, which is supposed to resolve activation errors automatically by updating the license from your account, but that system does not yet know how to handle Xamarin.Mac licenses and so errors out.

    This error will be fixed in 5.3 though it'll likely be a few more releases till XM uses the unified activation system. The current way to resolve XM activation errors is, as you discovered, to activate XM manually.

  • plynkusplynkus USMember

    That's great info, Michael. Thank you. (It's always a better feeling to understand there is a known issue and not some kind of environment corruption, etc. I appreciate you taking the time to explain it.)

Sign In or Register to comment.