IssueTracker

Not able to edit the description.

Here is what crash is related to ->

        val focusRequester = remember { FocusRequester() }
        PinInput(
            pageSidePadding = pageSidePadding,
            modifier = modifier.focusRequester(focusRequester),
            length = noOfBoxes,
            onValueChanged = change,
            value = text,
        )
        // LaunchedEffect(Unit) {
        //     focusRequester.requestFocus()
        // }

This launched effect is causing the issue in my case.

Can you create a smaller repro with a simplified implementation of PinInput? Does PinInput use a Modifier.focusable() internally?

Sure will add.

Found the root cause of the issue.

I basically have a text field which is not visible.

TextField(
            value = value,
            onValueChange = {
                if (it.length <= length) {
                    if (it.all { c -> c in '0'..'9' }) {
                        onValueChanged(it)
                    }
                    if (it.length >= length) {
                        keyboard?.hide()
                    }
                }
            },
            // Hide the text field
            modifier = modifier
                .focusRequester(focusRequester = focusRequester)
                .size(0.dp) // trouble causing line,
            keyboardOptions = KeyboardOptions(
                keyboardType = KeyboardType.NumberPassword,
            ),
        )

There is a launchedeffect at the end of it's parent composable which requests the focus.

LaunchedEffect(Unit) {
            focusRequester.requestFocus()
        }

Crash happens with the mentioned error, but If I change the size to a non zero value, crash doesn't occur anymore.

For my usecase textfield is just a placeholder, data in textfield is beautified and then shown separately.

Seeing a similar crash in our app. We do request focus as mentioned previously but haven't been able to confirm if this is what is causing the crash.

Fatal Exception: java.lang.IllegalStateException: Expected BringIntoViewRequester to not be used before parents are placed.
       at androidx.compose.foundation.gestures.ContentInViewModifier.calculateRectForParent(ContentInViewModifier.java:45)
       at androidx.compose.foundation.relocation.BringIntoViewResponderModifier$bringChildIntoView$parentRect$1.invoke(BringIntoViewResponderModifier.java:17)
       at androidx.compose.foundation.relocation.BringIntoViewResponderModifier$bringChildIntoView$parentRect$1.invoke(BringIntoViewResponderModifier.java:17)
       at androidx.compose.foundation.relocation.AndroidBringIntoViewParent.a(AndroidBringIntoViewParent.java:4)
       at androidx.compose.foundation.relocation.BringIntoViewResponderModifier$bringChildIntoView$2$2.invokeSuspend(BringIntoViewResponderModifier.java:45)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(BaseContinuationImpl.java:8)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.java:100)
       at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.java:22)
       at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.java:22)
       at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.java:2)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:223)
       at android.app.ActivityThread.main(ActivityThread.java:7703)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:952)

Still a rare issue on Compose 1.8 last week snapshots.

Exception java.lang.IllegalStateException: Expected BringIntoViewRequester to not be used before parents are placed.
  at androidx.compose.foundation.internal.InlineClassHelperKt.throwIllegalStateException (InlineClassHelper.kt:26)
  at androidx.compose.foundation.gestures.ContentInViewNode.calculateRectForParent (ContentInViewNode.kt:462)
  at androidx.compose.foundation.relocation.BringIntoViewResponderNode$bringChildIntoView$parentRect$1.invoke (BringIntoViewResponder.kt:171)
  at androidx.compose.foundation.relocation.BringIntoViewResponderNode$bringChildIntoView$parentRect$1.invoke (BringIntoViewResponder.kt:171)
  at androidx.compose.foundation.relocation.BringIntoViewResponder_androidKt$defaultBringIntoViewParent$1.bringChildIntoView (BringIntoViewResponder.android.kt:29)
  at androidx.compose.foundation.relocation.BringIntoViewResponderNode$bringChildIntoView$2$2.invokeSuspend (BringIntoViewResponder.kt:192)
  at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33)
  at kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:101)
  at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch (AndroidUiDispatcher.android.kt:79)
  at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch (AndroidUiDispatcher.android.kt:41)
  at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run (AndroidUiDispatcher.android.kt:57)
  at android.os.Handler.handleCallback (Handler.java:938)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:210)
  at android.os.Looper.loop (Looper.java:299)
  at android.app.ActivityThread.main (ActivityThread.java:8118)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:556)

Is it a possible workaround to set the Textfield to 0.01.dp or even lower, and set it's alpha to 0f? If the size is an issue, it could be put in a box with the actually displayed component being on top of it, assuming it is bigger than 0.01.dp?

If the aforementioned textfield is within a lazycolumn, we solved this crash by first making sure that we scroll to that component (becomes visible on the screen), then call the focusrequester. It is quite tricky, as LazyColumn does not really offer a good way of scrolling to a specific composable, especially if the LazyColumn has both item {} and later below somewhere items() as well.