Bug 25022 - License fails if no network connection
Summary: License fails if no network connection
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2014-12-03 01:21 UTC by Mark Fredrickson
Modified: 2017-08-23 21:33 UTC (History)
4 users (show)

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

Screenshot of bug not fixed. (78.11 KB, image/png)
2015-05-03 17:54 UTC, Mark Fredrickson

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 Mark Fredrickson 2014-12-03 01:21:32 UTC
I get the following error when I do not have a network connection. Here are the steps I can do to recreate it.

1. Activate my laptop (new registration license)

2. Disable the network

3. Reboot

4. Open Xamarin 

5. Xamarin displays an Unhandled Activation Error (see below)

6. Reconnect the network

7. Open Xamarin

8. Start to debug my app

9. Xamarin displays the Xamarin account login screen

10. I login and I get another licensed computer (now I have my laptop licensed twice)

This is occurring when I'm in the field trying to debug my app and has caused me to loose significant development time and is starting to impact my schedule.

The error:

System.Exception: Could not load machine data: monodroid: error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.InvalidOperationException: The source sequence is empty
  at System.Linq.Enumerable.First[String] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 
  at Xamarin.Licensing.PlatformActivation.GetRegistrationXml (Mono.Touch.Activation.Common.License license) [0x00000] in <filename unknown>:0 
  at Xamarin.Licensing.PlatformActivation.ShowDataFile () [0x00000] in <filename unknown>:0 
  at Xamarin.Licensing.PlatformActivation.ProcessOptions () [0x00000] in <filename unknown>:0 
  at Monodroid.Arguments.Parse (IEnumerable`1 argv) [0x00000] in <filename unknown>:0 
  at Monodroid.MainClass.Main (System.String[] argv) [0x00000] in <filename unknown>:0
   at Xamarin.Components.Ide.Activation.ActivationService.GetErrorWorkflow(LicenseSyncResult[] results, Boolean ignoreSyncErrors)
   at Xamarin.Components.Ide.Activation.ActivationService.<GenerateFullWorkflowSequence>d__89.MoveNext()
   at Xamarin.Components.Ide.Activation.ActivationDialog.DisplayWorkflowStep(ActivationWorkflowStep step)
   at Xamarin.Components.Ide.Activation.ActivationDialog.<>c__DisplayClass13.<StartSpinnerTaskAndScheduleContinuation>b__12(Task t)
Comment 1 Jonathan Pryor 2014-12-18 09:40:57 UTC
Fixed in activation/0974e30d and monodroid/4311053e.
Comment 2 Mark Fredrickson 2014-12-19 01:52:11 UTC
It's still happening. What do I need to do to get it fixed on my laptop?
Comment 3 Jonathan Pryor 2014-12-19 10:06:49 UTC
"FIXED" doesn't mean that the fix is now available. FIXED means that it has been fixed *internally*, giving QA a chance to test it. Once QA is satisfied, the bug will be marked VERIFIED, and at some later point in time the fix will actually be shipped and usable by customers.

There is no current ETA on when this fix will be shipped to customers. Check the release notes to see what bugs are fixed.
Comment 4 Peter Collins 2015-01-22 15:17:36 UTC
This fix is included in XA 5.0, and will be part of an XA 5.0 preview release that will be published on the web within a week or so.
Comment 5 Mark Fredrickson 2015-03-12 00:34:13 UTC
I don't see it in the Bug Fixes section of XA 5.0 notes - http://developer.xamarin.com/releases/android/xamarin.android_5/xamarin.android_5.0/.
Comment 6 Jonathan Pryor 2015-03-12 09:00:02 UTC
Comment #4 is mistaken. The fix will be included in Xamarin.Android 5.1.
Comment 7 Mark Fredrickson 2015-05-03 17:54:40 UTC
Created attachment 11039 [details]
Screenshot of bug not fixed.

Still not fixed in 5.1. See attached screenshot.
Comment 8 Mark Fredrickson 2015-05-03 17:55:24 UTC
See previous comment #7.
Comment 9 Peter Collins 2015-12-02 18:11:07 UTC
@Mark are you still encountering this activation issue? I'm not certain that we managed to reproduce the exact scenario you're describing here, however an attempt at fixing this issue should have been available in stable as part of XA 5.1.
Comment 10 Mark Fredrickson 2015-12-12 00:56:54 UTC
The error still occurs unless you follow the linked instructions and copy the license file into the appropriate folder prior to starting VS offline. So I think you can close this bug.

Comment 11 Cody Beyer (MSFT) 2017-08-23 21:33:50 UTC
This issue should not impact the latest versions