Fixed
Status Update
No update yet.
Comments
da...@google.com
I was able to repro locally using the snippet in #1. The slide should never be applied to the content for state == 0, i.e. the green box.
Will take a look. Thanks for the repro steps, Jeremy.
ap...@google.com
I'm having an issue with Compose navigation-animation which might be caused by this.
I have two screens: List and Details.
List screen uses default transitions.
Details screen uses the following transitions:
enterTransition = {
slideIntoContainer(
AnimatedContentScope.SlideDirection.Up,
animationSpec = tween(400)
)
},
popExitTransition = {
slideOutOfContainer(
AnimatedContentScope.SlideDirection.Down,
animationSpec = tween(200)
)
},
The video is showing the bug vs expected. It's hard to describe: after clicking the back button before the transition to the Details screen was completed, the List screen moves up a little.
Description
@Entity(tableName = "purchase_table", ignoredColumns = arrayOf("mParsedJson"))
class CachedPurchase(mOriginalJson: String, mSignature: String) : Purchase(mOriginalJson, mSignature) {
@PrimaryKey(autoGenerate = true)
var id: Int = 0
}
Error:
Room actually generates the correct code, but the compiler still complains about the ignored fields, i.e., "mParsedJson"