IssueTracker

Simple example would be:

var showLiveContent by rememberSaveable { mutableStateOf(true) }
LaunchedEffect(Unit) {
    delay(2000)
    showLiveContent = false
}

val layer = rememberGraphicsLayer()
Box(Modifier.size(200.dp)) {
    if (showLiveContent) {
        Column(Modifier.drawWithContent {
            layer.record { this@drawWithContent.drawContent() }
            drawLayer(layer)
        }) {
            Text("ComposeText")
            AndroidView(factory = {
                TextView(it).also { it.text = "ViewText" }
            })
        }
    } else {
        Canvas(Modifier.fillMaxSize()) {
            drawLayer(layer)
        }
    }
}

After the flag switched to false, the text drawn by the Text composable will continue to be displayed, but the text drawn by the TextView is not.

The main side effect of it is we don't support disappearance animations via Modifier.animateItem() for the View based content in all the lazy layouts.

This issue was discussed during the design of the list item animations in go/compose-list-item-animations - Issue C, Option 2. Quote from there:

"We will also need some adjustments on how we handle AndroidViews inside items. It is especially important for TextureView or SurfaceView (for example video players). Once we remove a View from the views hierarchy its surface is destroyed. We can solve it by keeping views attached until the animation finishes. We already introduced the AndroidView(onRelease = {}) callback which should be used by the users when the view is fully released. And we already keep views after the AndroidView is disposed when we reuse them during scrolling. In this case we will continue using the same already provided callbacks and will call onRelease only after the animation finishes."

As part of this ticket we need to make this use case work. It will likely require:

• adding a new callback to GraphicsLayer so one can subscribe to the "discardDisplayList" event of the layer (note that we can't just use the "release" here, as when the user of the layer called release on it, it doesn't necessary mean this layer is not displayed anywhere anymore, as we track the parent-child usages and keep the layer's display list until it is not used by any parent as well)
• The lifecycle of the AndroidView composable's callback should be altered to wait for the parent layer to discard its display list before calling onRelease()