New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/mobile/app: android:screenOrientation is not honored #10943
Comments
I have had a change for this sitting around for a while, but I'm working on proper testing first. |
CL https://golang.org/cl/16150 mentions this issue. |
@crawshaw while I submitted CL 16150, I don't consider it complete (I think there's a tag the Go team uses for this but I don't recall, this is my first CL). Specifically, testing needs a definitive target and not just whatever's installed on a developers machine as in the CL. The test should enforce use of a specific build-tool version as a method of declaring the cmd's intended output compatibility. I considered the current test broken but there are useful bits that should remain describing the format. The comments of As a frame of reference, I have the following build tool versions installed locally and did a byte compare of manifest output:
All resource identifiers that can not be extracted from gomobile's minimum target (api-9?) should be excluded currently. This concern is a separate issue with gomobile since resource identifiers are hard-coded but contain no information wrt the api level the identifier was introduced. This may lead to invalid manifests containing resource identifiers for an api level higher than the declared target api of a developers manifest. I'm unaware of the defined behaviour in such a case. This should not affect |
@dskinner while I'm sure we could do more, your CL is already a huge improvement. Thank you! |
Ok, I think some of those issues I mentioned should maybe get their own issue for tracking then as they have some unanswered questions that would only delay this CL for little reason. I'll follow up with that now. |
Testing BinaryXML for the change was non-trivial as the first 4 bytes of gomobile output did not match the latest version of aapt's output. A new approach to testing compatibility was added based on how the aapt tool pretty prints xmltree of manifest's contents. Fixes golang/go#10943 Change-Id: I5c60af10931d9693dbeaff66f23a69042a78e8fa Reviewed-on: https://go-review.googlesource.com/16150 Reviewed-by: David Crawshaw <crawshaw@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Testing BinaryXML for the change was non-trivial as the first 4 bytes of gomobile output did not match the latest version of aapt's output. A new approach to testing compatibility was added based on how the aapt tool pretty prints xmltree of manifest's contents. Fixes golang/go#10943 Change-Id: I5c60af10931d9693dbeaff66f23a69042a78e8fa Reviewed-on: https://go-review.googlesource.com/16150 Reviewed-by: David Crawshaw <crawshaw@golang.org> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
I have an application with the following AndroidManifest.
android:screenOrientation="landscape"
is ignored. The application starts in the portrait mode and screen orientation changes as I rotate the device. This value must have been handled during the EGLSurface creation and configuration changes on Android.cc/ @crawshaw
The text was updated successfully, but these errors were encountered: