Closed marcelskotnickifm closed 5 months ago
Doesn't seem like anything related with the library.
I'm closing, let me know if you really think it is related to CD and why.
@raamcosta Because using it (snackbarHandler
) in @Destination<RootGraph>
screen crashes the app, meanwhile using it outside of navigation scope works just fine. As I said, it only happens when using the latest compose, CD & material3 versions.
As you can see in the stack trace, there’s no mention of compose destinations package.
I don’t have time to get to the root cause, but I’m confident this is not related to this library. Maybe it is with official compose navigation (which we use internally).
If you’re still convinced it’s related to this library directly, try a sample with official library directly and no compose destinations. If the problem doesn’t exist there, do let me know.
Hi! First of all great work, much appreciated đź‘Ź I am creating a Snackbar-like component
where
Snackbar
isand the stack trace to the crash (happens the moment app opens) is
while using
Placing
Snackbar
inScaffold
'ssnackbarHost
didn't change a thing. Removing references fromAnimatedVisibilityScope
to the outside fields and values stops the app from crashing , but of course breaks the snackbar's look & behavior. Changing dependencies' versions tomakes everything work properly, but update any of them and the issue arise.