BottomSheet fly away with visibility change when using animateLayoutChanges
See original GitHub issueOverview
After a few research I found more devs with the same problem.
In this stackoverflow thread a guy from Google suggests to use TransitionManager.beginDelayedTransition(bottomSheet);
but the solution don’t works as expected.
To simplify I had create a repository with the problem: https://github.com/extmkv/BottomSheetExample
Issue Analytics
- State:
- Created 5 years ago
- Reactions:29
- Comments:6
Top Results From Across the Web
BottomSheet fly away with visibility change - Stack Overflow
I ran into this, took a while to figure out what was the cause. It's because you're using android:animateLayoutChanges, which surfaces a bug...
Read more >Android – BottomSheet fly away with visibility change – iTecNote
It's because you're using android:animateLayoutChanges, which surfaces a bug in either BottomSheetBehavior or CoordinatorLayout. Remove it and the BottomSheet ...
Read more >Reveal or hide a view using animation - Android Developers
Utilizing animations can slow down the changes and draw the user's eye ... For the view that is being faded in, set its...
Read more >Android Bottom Sheet Behavior and Animated Button on Top ...
You can add BottomSheetCallback for detecting state changes and getting slide offset. We will use the last one for correctly animating our ...
Read more >Diff - 97b3163085..6fce3ce354 - chromium/src - Git at Google
-133,11 +133,11 @@ # Three lines of non-changing comments so that # the ... + Use of this source code is governed by...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Are there any plans on fixing this issue?
Anyone found a solution?