Oscar

Moved the relative position parameter to a more common level. Marked constructors internal. Renamed BaseKeyFramesScope to better reflect its purpose.

Which version of the library are you using? Have you tried removing the wrapContentWidth/Height modifiers? Ie: Just Modifier.layoutId("title") MotionLayout will default to wrapContent.

Taking another look at this, not sure if this is what you intended but it seems to do the trick in terms of the expected layout. ```kotlin @Preview @Composable private...

> I can confirm this, meanwhile solved it with `Spacer` function > > Possible related bug: if I use a nondefault bias for vertical chain with `ChainStyle.Packed`, e.g. `Packed(0.55f)`, I...

For the issue mentioned here, use 1.1.0-alpha03 in the meantime.

Reasoning is that this is likely a more common pattern than: `val constraintSet = if (isVisible) visibleConstraintSet else goneConstraintSet`

Which Compose version is this? Haven't been able to repro on 1.0.0 or even 1.1.0. I'm using a very simple setup: ```kotlin @OptIn(ExperimentalMotionApi::class) @Preview @Composable fun CrashTest() { var sectionsState:...

Any chance one of the Composables in MotionLayout has a size Modifier? (size, sizeIn, defaultMin, fillMaxSize, etc) Does it still crash with Dimension.fillToConstraints instead of Dimension.matchParent?

No workaround other than sticking to 1.0.x It's a hard check that prevents us from remeasuring Composables during animation in some cases. I'll close this once we work out a...

Issue seems to be resolved when using 1.2.0-alpha08 Tho I see issues with custom properties. I'll keep this open until 1.2.0 hits stable or I'm able to guarantee no regressions...