Fixed
Status Update
Comments
te...@gmail.com <te...@gmail.com> #3
Which version? I don't see an option in 33.1.2
da...@gmail.com <da...@gmail.com> #5
Thanks!
wh...@gmail.com <wh...@gmail.com> #6
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Emulator 33.1.4
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
il...@google.com <il...@google.com>
fl...@gmail.com <fl...@gmail.com> #7
Thnx
jo...@onsalesit.com <jo...@onsalesit.com> #8
Gracias
dj...@gmail.com <dj...@gmail.com> #9
I have the same issue. I had enter animation as fade_in and exit animation as fade_out. For me temporary solution is change exit animation to 0, transaction now looks almost the same as with fade_out exit animation
mo...@google.com <mo...@google.com>
mo...@google.com <mo...@google.com> #10
Thank you for reporting this bug. I am able to reproduce it. It was caused when fixing another bug and this error wasn't caught during testing.
ra...@gmail.com <ra...@gmail.com> #11
Same issue. I had to roll back version to fix it
mo...@google.com <mo...@google.com> #12
Fix has been submitted and should be in the next public release.
kk...@google.com <kk...@google.com> #13
This bug has been fixed in Support Library 27.1.1.
al...@gmail.com <al...@gmail.com> #14
In the app that I am working on, this issue only occurs when pressing back (unwinding the transaction). The problem is still reproducible in 27.1.1. Does 27.1.1 fix the problem for others?
Description
Version used: 27.1.0
Theme used: AppCompat No ActionBar
Devices/Android versions reproduced on:
I currently use a base fragment transaction with the following code to animate fragment replacements by default from within a support fragment:
getFragmentManager()
.beginTransaction()
.setCustomAnimations(android.R.anim.fade_in, android.R.anim.fade_out, android.R.anim.fade_in, android.R.anim.fade_out);
This worked great on Support library version 27.0.2 and below. Version 27.1.0 however causes the replaced fragment to flicker for a second or so after the new fragment is shown.
The fragment transactions do NOT have setReorderingAllowed to true, NOR do they postpone any pending transitions.