Bug 37858 - [Android] ScreenOrientation.UserLandscape fails with "Unsupported ScreenOrientation value"
Summary: [Android] ScreenOrientation.UserLandscape fails with "Unsupported ScreenOrien...
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: General (show other bugs)
Version: 6.0.0
Hardware: PC Mac OS
: Highest normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2016-01-21 01:51 UTC by Kent Green [MSFT]
Modified: 2016-07-05 22:15 UTC (History)
5 users (show)

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


Attachments
IDE Logs & sample to reproduce error (295.42 KB, application/zip)
2016-01-21 01:51 UTC, Kent Green [MSFT]
Details

Description Kent Green [MSFT] 2016-01-21 01:51:59 UTC
Created attachment 14648 [details]
IDE Logs & sample to reproduce error

## Overview
From this enterprise desk case:
https://kb.xamarin.com/agent/case/248484

Customer reports that using the ScreenOrientation.UserLandscape fails to build the app. I was able to reproduce the issue by testing on my LG Volt API 19 device. 

## Code snippet
The orientation is set in the Activity flag
> [Activity(Label = "UserLandscape", MainLauncher = true, Icon = "@drawable/icon", 
> ScreenOrientation = ScreenOrientation.UserLandscape, LaunchMode = LaunchMode.SingleInstance,
> Theme = "@android:style/Theme.NoTitleBar")]

## Steps to reproduce
Attempt to build the app for an API 18 or higher device. The build fails with:
> Error: Error executing task GenerateJavaStubs: Unsupported ScreenOrientation value '11'. Parameter name: ScreenOrientation (UserLandscape)

## Expected behavior
The documentation states:
> "userLandscape" - "Added in API level 18"
- http://developer.android.com/intl/ru/guide/topics/manifest/activity-element.html

## Build Information
=== Xamarin Studio ===

Version 5.10.1 (build 6)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
Runtime:
	Mono 4.2.1 (explicit/6dd2d0d)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010102

=== Xamarin.Profiler ===

Version: 0.0.0.0
Location: /Applications/XamarinProfiler.Mac.app/Contents/MacOS/XamarinProfiler.Mac

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.Mac ===

Version: 2.4.0.109 (Business Edition)

=== Xamarin.Android ===

Version: 6.0.0.34 (Business Edition)
Android SDK: /Users/kentgreen/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		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)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.2

Java SDK: /usr
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.65-b01, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin.iOS ===

Version: 9.4.0.0 (Business Edition)
Hash: 7322991
Branch: master
Build date: 2015-12-08 16:20:29-0500

=== Build Information ===

Release ID: 510010006
Git revision: 0b60eecdb531933734519c13257d16a780274aab
Build date: 2015-12-04 20:28:20-05
Xamarin addins: 9876fd7c9837977178411ec7375b4352c0a0d6af
Build lane: monodevelop-lion-cycle6-baseline

=== Operating System ===

Mac OS X 10.10.5
Darwin Kents-Macbook-Pro.local 14.5.0 Darwin Kernel Version 14.5.0
    Wed Jul 29 02:26:53 PDT 2015
    root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64

## Additional Info
Adding sample from customer & IDE logs from my reproduction of the issue with that sample.

The customer also reproduced it in XVS 3.11.1594 / XA 5.1.7.12
Comment 2 Kent Green [MSFT] 2016-01-21 18:59:35 UTC
The user also reported the same behavior with these elements:
> Locked
> FullUser
> UserPortrait
> UserLandscape

These all are essentially the same as this bug, though it is 4 separate elements instead of just one. Please let me know if it would be preferable to split these other occurrences into a separate bug report.

Note You need to log in before you can comment on or make changes to this bug.