A modern programming language that makes developers happier.

kotlinlang

I'm doing something kind of hacky and introducing a weird tree in compose that looks like the following: "Column [ AndroidView [ FrameLayout [ setContent @Composable[ TextField ] ] ] ] ". Now, when I click and try to type on this textfield that resides in a framelayout which resides in an AndroidView Composable, an exception is thrown.
```java.lang.IllegalStateException: KeyEvent can't be processed because this key input node is not active.```
Is this worthy of filing a bug? Or is it too weird of a use case? Should compose never be entangled in different layers with the old View system like this?

There’s a bug filed for that already. I think it’s fixed for next release

<https://issuetracker.google.com/issues/165034731>

Btw, I don’t think it’s a weird use case. The main use case of Compose right now is to integrate with existing code, over writing purely compose apps. Or at least that’s what I heard somewhere I can’t remember where from.