Fixed
Status Update
Comments
ry...@google.com <ry...@google.com>
ch...@google.com <ch...@google.com>
ah...@gmail.com <ah...@gmail.com> #2
Is this really a P1? This seems less priority than the perf work that I am doing but if it is a P1 I will block that and work on this.
ch...@google.com <ch...@google.com> #3
I'm happy to move it to a p2, but it seems like a pretty big correctness issue that we should take a look at in the near future. I'm also happy to help look at this myself if you can give me some pointers on what the issue may be
ap...@google.com <ap...@google.com> #4
This is not simple as and will change once Jim lands the threading of the composer.
ke...@gmail.com <ke...@gmail.com> #5
Sure thing, thanks for the context!
For anyone running into this issue, in the meantime the simple workaround is just consuming the ambient inside the body of the function, you don't explicitly need to use the returned value anywhere.
For anyone running into this issue, in the meantime the simple workaround is just consuming the ambient inside the body of the function, you don't explicitly need to use the returned value anywhere.
Description
Jetpack Compose release version: 1.1.0 & 1.2.0-alpha03
Here's a sample code to reproduce the issue:
A crash occurs with the next stack trace: