Fixed
Status Update
No update yet.
Comments
il...@google.com
da...@gmail.com
Still crashing with Compose 1.7.4.
I also tried moving sharedElement to BoxWithConstraints (rather than in its content), but did not help.
So the layout hierarchy looks like this (with more details and with "..." I replaced series of "normal" layouts):
NavHost -> ... -> AnimatedVisibility -> ... -> BoxWithConstraints with sharedElement -> some content
\> ... -> AnimatedVisibility -> ... -> LazyList -> ... -> Animated Visibility -> Selection container -> BoxWithConstraints with sharedElement -> some content
Any ideas?
I also tried moving sharedElement to BoxWithConstraints (rather than in its content), but did not help.
So the layout hierarchy looks like this (with more details and with "..." I replaced series of "normal" layouts):
NavHost -> ... -> AnimatedVisibility -> ... -> BoxWithConstraints with sharedElement -> some content
\> ... -> AnimatedVisibility -> ... -> LazyList -> ... -> Animated Visibility -> Selection container -> BoxWithConstraints with sharedElement -> some content
Any ideas?
il...@google.com
il...@google.com
In your BoxWithConstraints do you do any conditional composition? Things like:
if (constraintsExceedsCertainThreshold) composeSomeContent() else someOtherContent()
Description
Version used:1.0.0-alpha07
Devices/Android versions reproduced on: Emulator API 28, Xiaomi MI A1 8.1 (Android One)
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue. - ATTACHED
Clicking on a Notification with PendingIntent created by NavDeepLinkBuilder uses the arguments of the last Notification created. For example: If you created notifications with fragment arguments 1, 2 and 3, then no matter which notification you click on, the fragment is started with argument 3.