Hello, using KMP Compose 1.8.2 I am having an issu...

# compose-ios

[Tristan]

Hello, using KMP Compose 1.8.2 I am having an issue with text fields.
When I tap on a text field I get this error

Can't show file for stack frame : <DBGLLDBStackFrame: 0x149e1ea90> - stackNumber:0 - name:kfun:kotlin.coroutines.Continuation#<get-context>(){}kotlin.coroutines.CoroutineContext-trampoline. The file path does not exist on the file system: /opt/buildAgent/work/2d153abd4d2c0600/kotlin/libraries/stdlib/src/kotlin/coroutines/Continuation.kt

And the text field I am using

var textFieldValue by remember {
    mutableStateOf("")
}
                
OutlinedTextField(
    value = textFieldValue,
    onValueChange = { textFieldValue = it },
    singleLine = true,
    modifier = Modifier.width(160.dp)
)

And my imports

implementation(compose.runtime)
            implementation(compose.foundation)
            implementation(compose.material3)
            implementation(compose.ui)
            implementation(compose.components.resources)
            implementation(compose.components.uiToolingPreview)

Do you think I am missing something? Other UI elements work fine (buttons and checkboxes)

[Andrei Salavei]

Could you please provide a small reproducer and upload it on GitHub?
Also, feel free to file an issue in our YouTrack.

[Tristan]

Thank you. I'll try this. I have not been able to reproduce outside of my project yet.

[Tristan]

I found my issue:

implementation("org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-compose:2.9.2")

Downgrading it to 2.9.1 solves the issue

[DevOpsCraftsman]

We are using the 2.9.1, and we still have the crash...

I wonder what made you believe it was this?

[DevOpsCraftsman]

We have a similar issue. If you were able to share how you did diagnose it, maybe you could do it too.

[Andrei Salavei]

@DevOpsCraftsman, check what library versions where actually loaded by the gradle - sometimes it loads incompatible versions If you' can provide a reproducer, we'll take a look.

[DevOpsCraftsman]

We’ve tested with a minimal example, impossible to reproduce the crash.

We were focusing on the android side, and we were not thoroughly testing the ios one, since its priority was lower…

We will perform a git bisect in the near future to find the root cause, and we will post the results here when done.

[Tristan]

@DevOpsCraftsman I removed my dependencies one by one, and as soon as I removed this one, I was able to tap on the text field. Then I reintroduced it, and looked for a version with which it would not crash. Going 1 version down was enough.