Closed IssaMansour closed 1 year ago
The issue is transitionSpec
param from AnimatedContent
had AnimatedContentScope
as it's receiver in previous compose versions but in the latest alpha version (1.5.0-alpha01+) the lambda receiver is AnimatedContentTransitionScope
. @saket should I create a PR?
Yes please! It'll break compatibility with older versions of compose but I guess I have no choice. AnimatedContent()
was marked as experimental afterall.
In 1.5.0-alpha, AnimatedContent is not marked as Experimental anymore.
It is exactly as you said! I also did the fix yesterday and added this lib manually and it works well.
Didn't do a PR cause I did a quick and dirty test.
Thanks guys! When do you think it will be available? cc. @saket
The issue is
transitionSpec
param fromAnimatedContent
hadAnimatedContentScope
as it's receiver in previous compose versions but in the latest alpha version (1.5.0-alpha01+) the lambda receiver isAnimatedContentTransitionScope
. @saket should I create a PR?
Alright I just published 2.0.0
by promoting 2.0.0-rc02
to stable. We can now make breaking changes in the next version by updating compose ui to 1.5.0-alpha01
.
Fwiw you can quickly unblock yourself by switching to @kasem-sm's fork by using jitpack:
Released as part of https://github.com/saket/cascade/releases/tag/2.1.0. Thanks everyone!
FWIW I just published a new snapshot that uses compose ui 1.5.0-beta02
implementation "me.saket.cascade:cascade-compose:2.2.0-SNAPSHOT"
Scratch that, v2.2.0
is out: https://github.com/saket/cascade/releases/tag/2.2.0
Scratch that,
v2.2.0
is out: https://github.com/saket/cascade/releases/tag/2.2.0
Can confirm. The crash is now fixed
Hello,
I'm having a crash after updating from
androidx.compose.material3:material3:1.1.0-beta02
toandroidx.compose.material3:material3:1.2.0-alpha01
.Here the stacktrace:
Any idea how to fix it? I want to keep this upgraded version of material3 as it fixed other issues.
Thanks!