Bug 59309 - [Android Oreo] Automatic Target Android Version is not recognized with specific features
Summary: [Android Oreo] Automatic Target Android Version is not recognized with specif...
Status: RESOLVED DUPLICATE of bug 35208
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 8.0 (15.4)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2017-09-07 20:28 UTC by Gonzalo Martin
Modified: 2017-09-07 21:07 UTC (History)
3 users (show)

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

vs2017 logs (78.46 KB, application/zip)
2017-09-07 20:28 UTC, Gonzalo Martin

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:

Comment 1 Jon Douglas [MSFT] 2017-09-07 20:59:42 UTC
I can CONFIRM this behavior and I believe the main cause has to deal with the following bug:


I believe the next step is to write a spec on this issue to see if we can fix this common pain point in a future version of Xamarin.Android. For future reference, it is advised to explicitly set the `targetSdkVersion`. We should probably update our documentation on this subject as well as it also leaves users astray.

Comment 2 Peter Collins 2017-09-07 21:06:22 UTC

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