Status Update
No update yet.
Comments
am...@google.com
Here's another log file from the real development project, reproduced using the method with 1-finger touch described above.
to...@gmail.com
Thanks for the bug report. I was able to repro and I have a fix in review.
am...@google.com
Great! Do you know in which version it'll be updated/fixed and available for download?
so...@gmail.com
Issue is not fully fixed!!!
Configuration is updated but DisplayMetrics are still not :(
I suggested a workaround both in
updateConfiguration(config, Resources.getSystem().getDisplayMetrics());
I can see in your code that you only added this call:
updateConfiguration(config, null);
Obviously the result in that Configuration is updated (config), but not DisplayMetrics (null).
Please reopen the bug.
Configuration is updated but DisplayMetrics are still not :(
I suggested a workaround both in
updateConfiguration(config, Resources.getSystem().getDisplayMetrics());
I can see in your code that you only added this call:
updateConfiguration(config, null);
Obviously the result in that Configuration is updated (config), but not DisplayMetrics (null).
Please reopen the bug.
le...@gmail.com
I just checked with the com.android.support:design:23.3.0 library, and it doesn't crash any more but the bug is still there, resulting the UI issue described in my initial post above (i.e. the snackbar doesn't come back to its original position).
In the official page of Support Library (http://developer.android.com/tools/support-library/index.html ) it's mentioned that you've fixed the crash issue but nothing about the ugly UI bug. Was it so hard or you guys just overlooked/ignored it?
In the official page of Support Library (
mi...@gmail.com
chrisbanes@ you marked internal bug as closed. Is this fixed in 23.3.0?
Description
Version used: 23.2.0
Theme used: Theme.AppCompat.Light.DarkActionBar
Devices/Android versions reproduced on:
- LG Nexus 5X / Android 6.0.1
- BQ Aquaris X5 / Android 5.1.1
- BQ Aquaris E5 / Android 4.4.2
When an Activity that extends AppCompatActivity is set up with the attribute "android:configChanges" set to "orientation|screenSize" in its AndroidManifest file, the value returned by AppCompatActivity.getResources().getConfiguration().orientation is always the one that the app had when it started regardless of the current orientation.
This doesn't happen with previous AppCompat library versions.
Steps to reproduce with the attached code sample:
- Open the app
- Tap "Get Orientation"
- Rotate the device to the opposite orientation.
- Tap "Get Orientation" again
- Verify that the same orientation value is returned in both orientations.