Bug 16285 - XA emits spurious activation error when set to use latest SDK
Summary: XA emits spurious activation error when set to use latest SDK
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.10.1
Hardware: PC Mac OS
: Highest critical
Target Milestone: 4.10.2
Assignee: Jonathan Pryor
URL:
: 16390 16640 16641 16847 17041 17328 17374 ()
Depends on:
Blocks:
 
Reported: 2013-11-15 16:46 UTC by Mikayla Hutchinson [MSFT]
Modified: 2014-01-30 17:29 UTC (History)
10 users (show)

Tags:
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:
Status:
VERIFIED FIXED

Description Mikayla Hutchinson [MSFT] 2013-11-15 16:46:00 UTC
It seems that XA is emitting a spurious activation error when et to use the latest SDK.

http://forums.xamarin.com/discussion/10265/invalid-or-corrupt-license-xamarin-starter-free#latest
Comment 1 Mikayla Hutchinson [MSFT] 2013-11-19 15:10:22 UTC
This has also come up in several other forum posts and support requests. Since it incorrectly triggers the activation system even when the license is valid, it causes activation loops.
Comment 3 Mikayla Hutchinson [MSFT] 2013-11-19 15:21:55 UTC
Note: it should be possible to work around this by uninstalling API level 19 from the Android SDK Manager.
Comment 4 Peter Collins 2013-11-20 17:39:45 UTC
Was able to reproduce on Windows, but not on OSX mountain lion or mavericks.

1) Install API 19 packages via Android SDK Manager
2) Open XS, create a new Android Template
3) http://screencast.com/t/kXXdYWgz

AndroidTools and IDE logs:
https://gist.github.com/pjcollins/a85f0a9b26299c07637c
Comment 5 Jonathan Pryor 2013-11-20 21:57:42 UTC
Fixed in monodroid/79ca4d61.
Comment 6 Mikayla Hutchinson [MSFT] 2013-11-21 15:20:10 UTC
*** Bug 16390 has been marked as a duplicate of this bug. ***
Comment 7 Mikayla Hutchinson [MSFT] 2013-11-21 16:47:49 UTC
Can we also fix the issue that an XA0000 error caused an XA90xx activation error for no reason?
Comment 9 Jonathan Pryor 2013-11-21 17:57:59 UTC
The issue in Comment #7 should be addressed in monodroid/d8d8d349.
Comment 11 Akhilesh kumar 2013-12-02 13:29:06 UTC
We have checked this latest build:

XS 4.2.2(Build 2) 
X.Android 4.01.02005

Android SDK Install API 19 packages

Screencast: http://screencast.com/t/1HbrnHrYS

Now, we are able to create application on XS and not getting any activation error.

Hence, changing its status as Verified Fixed.
Comment 12 Keith Longwell 2013-12-05 23:00:25 UTC
Hummm,

I never had the issue until I have updated to 4.2.2 today.  Now I am getting this message over and over every time I add a new file, or save or anything.

I tried deleting API 19 (which I had to install after the last update for the .asmx files to load properly).

So now I'm back on SDK 18 with 4.2.2 because it's working.

(see my notes here http://forums.xamarin.com/discussion/11044/compile-made-me-re-login-and-said-using-on-2-computers-of-2-allowed#latest )
Comment 13 Jonathan Pryor 2013-12-06 10:40:05 UTC
@Keith: Xamarin.Android 4.10.2 contains the fix, which is currently in the Alpha and Beta channels (not yet Stable).
Comment 14 Mikayla Hutchinson [MSFT] 2013-12-06 17:56:51 UTC
*** Bug 16640 has been marked as a duplicate of this bug. ***
Comment 15 Mohit Kheterpal 2013-12-10 07:36:39 UTC
*** Bug 16641 has been marked as a duplicate of this bug. ***
Comment 16 Jonathan Pryor 2013-12-17 12:26:13 UTC
*** Bug 16847 has been marked as a duplicate of this bug. ***
Comment 17 Mikayla Hutchinson [MSFT] 2014-01-03 16:35:32 UTC
*** Bug 17041 has been marked as a duplicate of this bug. ***
Comment 18 Mikayla Hutchinson [MSFT] 2014-01-20 14:31:21 UTC
*** Bug 17328 has been marked as a duplicate of this bug. ***
Comment 19 PJ 2014-01-30 17:29:22 UTC
*** Bug 17374 has been marked as a duplicate of this bug. ***