Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 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.
The "Compile using Android version", "Minimum Android to Target" and "Target Android Version" drop-down menus are missing Android SDK 3.2.
## Steps to Reproduce:
1. Create an android application in Visual Studio.
2. Right-click on the project and choose Properties.
3. Go to the "Application" tab.
4. Select any of the above drop-down menus.
## Actual Results:
SDK 3.2 is missing from the list.
## Expected Results:
SDK 3.2 should be listed.
## Build Date & Platform:
VS 2013 Update 2
Checked, Android SDK 3.2 is missing in the compile target menu.
Xamarin 220.127.116.11 (d3cf238e3845e930e312b6ec9b4c6c5437c33067)
This is By Design. Each API level we ship bindings for adds ~50MB to the on-disk install (and then some to the compressed .msi), and we're already shipping 11 API level bindings (making for a gigantic installed size and installer size).
As it is, we want to _reduce_ the number of bindings we ship, though we won't remove any for the foreseeable future.
Furthermore, Honeycomb has so little representation that it's no longer visible on the Platform Versions dashboard. (When we first made the decision to skip shipping v3.2 bindings, it only had ~0.2%., while v3.1 was at least over 1%.)
Consequently we don't see any significant reason to include bindings for Android v3.2.