Bug 23814 - Android Designer should default to Target SDK theme, not highest
Summary: Android Designer should default to Target SDK theme, not highest
Status: RESOLVED DUPLICATE of bug 23924
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.18.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2014-10-14 09:29 UTC by Jeremy Kolb
Modified: 2014-10-19 20:41 UTC (History)
3 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:
RESOLVED DUPLICATE of bug 23924

Description Jeremy Kolb 2014-10-14 09:29:02 UTC
I'm sick of the theme always coming up as Android L when my target is 19.  I then have to change the theme in every single designer window to 19.
Comment 1 Sunil Kumar 2014-10-14 10:15:05 UTC
I have tried to reproduce this issue and getting the same behavior. I followed below steps to reproduce this issue:

1. Open XS.
2. Create a Android application.
3. Set the application target API 19.
4. Open the existing designer or add new designer and open it.

Android designer is opening with Android L(v21) theme. We are getting the same issue on Windows with XS and VS.

Screencast: http://www.screencast.com/t/TFBF0DqG2

I’ll need confirmation from the developer if this is a bug. Leaving as NEW for now.

Environment info: 
=== Xamarin Studio ===

Version 5.5 (build 227)
Installation UUID: 561c7a69-0a91-4bae-ad7c-f0c79d594337
Runtime:
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Xamarin.Android ===

Version: 4.18.0 (Business Edition)
Android SDK: /Users/tajinder/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.iOS ===

Version: 8.2.0.203 (Business Edition)
Hash: 6049af6
Branch: 
Build date: 2014-10-12 21:49:14-0400

=== Xamarin.Mac ===

Version: 1.10.0.13 (Business Edition)

=== Build Information ===

Release ID: 505000227
Git revision: 7b721eeec7a2fa4c4f4de0ecd2aed4dc25edac95
Build date: 2014-10-02 15:53:38-04
Xamarin addins: 99ed56b428b31eba1efaace4d82188d6f334e6ca

=== Operating System ===

Mac OS X 10.8.4
Darwin Tajinders-iMac.local 12.4.2 Darwin Kernel Version 12.4.2
    Mon Jun 17 18:00:12 PDT 2013
    root:xnu-2050.45.8~1/RELEASE_X86_64 x86_64
Comment 2 Jeremy Kolb 2014-10-14 10:18:57 UTC
Right.  I would argue that this is a bug because you want to see what the UI will look like for the Android version you are targeting, not some arbitrary version that you don't support yet.
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2014-10-19 20:41:16 UTC
Whoops I just filed a duplicate of this (Bug 23924) and then found this existing bug. I'll mark this bug as a duplicate of the new bug just because it might come in handy to have the original reporter be a Xamarin employee.

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