Bug 16847 - XA0000: Could not determine $(TargetFrameworkVersion) for API level 19
Summary: XA0000: Could not determine $(TargetFrameworkVersion) for API level 19
Status: RESOLVED DUPLICATE of bug 16285
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.10.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-12-17 11:32 UTC by Allie Miller
Modified: 2013-12-17 12:26 UTC (History)
1 user (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 Allie Miller 2013-12-17 11:32:07 UTC
After updating the Android SDK Manager to the latest packages (Android SDK Tools 22.3 and Android SDK Platform Tools 19), the following error appears in both Visual Studio and Xamarin Studio when attempting to deploy a project: 

C:\Program Files
(x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2,2): Error
XA9010: Unable to determine license edition. (XA9010) (AndroidFirst)

C:\Program Files
(x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2,2): Error
XA0000: Could not determine $(TargetFrameworkVersion) for API level '19.'
(XA0000) (AndroidFirst)
Comment 2 Jonathan Pryor 2013-12-17 12:26:13 UTC
This will be fixed in 4.10.2, which is currently in Beta and should be hitting Stable "soon"...

*** This bug has been marked as a duplicate of bug 16285 ***