Status Update
Comments
pb...@google.com <pb...@google.com>
ap...@google.com <ap...@google.com> #2
After upgrading to kotlin 2.1.0 and bumping remaining dependencies, things seem to work as expected again. EDIT: My bad; was on the wrong branch. Those upgrades did NOT help.
ap...@google.com <ap...@google.com> #3
I think I managed to track it down further:
In my Child
composable, I'm actually hitting a TODO()
statement:
@Composable
fun Child(isLoading: Boolean, items: List<MyDataClass>) {
// ...
if (notYetSupported) {
TODO("This is not yet supported!")
}
// ...
}
It would seem that compose swallows this error and throws the above instead which is not very helpful.
ap...@google.com <ap...@google.com> #4
The "pending composition has not been applied" error generally means that composition continued despite something in the hierarchy previously throwing an exception. Here it looks like something is continuing a subcomposition unexpectedly, possibly a LazyList.
We should see if we can improve this error messaging. Can you send over a more complete example? The snippets here aren't fleshed out enough to reproduce this swallowing behavior.
pr...@google.com <pr...@google.com> #5
Triage notes: It feels like we're very close to having a repro case that we could run internally, but we don't know where the sub-composition is coming from.
Can you send over a more complete example?
Let's hold until we can get a stable repro case from the reporter. Could you send us a ZIP of the project that repros this issue? We'll close this out in a month if we don't get a response.
Bugjuggler: wait 1 month
Description
AndroidX tracking bug forhttps://crbug.com/373558938
This API will allow app developers to delete all browsing data for a given WebView profile, or delete all data for a specific site