IssueTracker

Looks like AndroidX tooling didn't catch this because it happened prior to migrating the development workflow to AndroidX. Should be avoidable in the future since we have API files checked in for 1.1.0, but for now this will need to be fixed and we'll want to do whatever we can to mitigate the breakage in the released artifact.

I guess you don't need extra reports but also fails for Measurer

androidx.constraintlayout.compose.Measurer: method 'void <init>()' not found
java.lang.NoSuchMethodError: androidx.constraintlayout.compose.Measurer: method 'void <init>()' not found
	at com.google.android.horologist.media.ui.screens.player.PlayerScreenKt.PlayerScreen(PlayerScreen.kt:273)

this is a Composable from a library

@Composable
public fun PlayerScreen(
    mediaDisplay: @Composable () -> Unit,
    controlButtons: @Composable () -> Unit,
    buttons: @Composable () -> Unit,
    modifier: Modifier = Modifier,
    background: @Composable BoxScope.() -> Unit = {},
) {
    Box(
        modifier = modifier
            .fillMaxSize(),
    ) {
        background()

        ConstraintLayout(
            modifier = Modifier.fillMaxSize(),
        ) {
            val (topSection, middleSection, bottomSection) = createRefs()

hi all, is there any plan or workaround for this issue? would it be possible to bring back the old signatures that were removed to facilitate the update ? we are starting getting transitive bumps from third parties that are breaking other third parties sdks.

I have a change ready and tested locally where I simply bring back the removed signatures into the class. The change fixes the breaking change coming with constraintlayout-core 1.1.0.

Should I proceed opening a proposal PR ?