-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Android app crashes on rotation to landscape #148
Comments
I'm a bit confused, i compiled a debug distro yesterday to track it On Thu, Aug 15, 2013 at 04:02:45PM -0700, Alexander Taylor wrote:
|
The rotate crash will happen if you use a target SDK higher than 12. The default in py4a is 8, so you will not notice this problem unless you specify --sdk in the build command. To fix this, we need to figure out what change in SDK 13 is causing the rotation to fail. Change information is at http://developer.android.com/reference/android/os/Build.VERSION_CODES.html#HONEYCOMB_MR2 |
"New FEATURE_SCREEN_PORTRAIT and FEATURE_SCREEN_LANDSCAPE features were introduced in this release. Applications that target previous platform versions are assumed to require both portrait and landscape support in the device; when targeting Honeycomb MR1 or greater the application is responsible for specifying any specific orientation it requires" Doh, maybe we just need to add these flags to the xml? >_> |
Did you try this fix with API <= 12 ? With API 13 and 14 it works, but with API 8,11, and 12 I get results like http://pastebin.com/7CZLwXZB |
#8f4d23a allows the APK to compile on API <= 12, but the resulting app crashes if you rotate the screen. |
Is this still open on API < 12? |
This happens to me too.
Below is adb logcat.
|
My kivy app crashes when rotated from portrait to landscape via phone rotation with the 'orientation=sensors' option. An example logcat output is at https://gist.github.com/inclement/6245730
I've tested with another (much simpler) app and got the same behaviour, and tshirtman reports also seeing it.
The text was updated successfully, but these errors were encountered: