(#) produceState calls should assign `value` inside the producer lambda !!! ERROR: produceState calls should assign `value` inside the producer lambda This is an error. Id : `ProduceStateDoesNotAssignValue` Summary : produceState calls should assign `value` inside the producer lambda Severity : Error Category : Correctness Platform : Any Vendor : Jetpack Compose Identifier : androidx.compose.runtime Feedback : https://issuetracker.google.com/issues/new?component=612128 Min : Lint 8.7+ Compiled : Lint 8.7+ Artifact : [androidx.compose.runtime:runtime-android](androidx_compose_runtime_runtime-android.md.html) Since : 1.5.0 Affects : Kotlin and Java files and test sources Editing : This check runs on the fly in the IDE editor Implementation : [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/compose/runtime/runtime-lint/src/main/java/androidx/compose/runtime/lint/ProduceStateDetector.kt) Tests : [Source Code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/compose/runtime/runtime-lint/src/test/java/androidx/compose/runtime/lint/ProduceStateDetectorTest.kt) Copyright Year : 2021 produceState returns an observable State using values assigned inside the producer lambda. If the lambda never assigns (i.e `value = foo`), then the State will never change. Make sure to assign a value when the source you are producing values from changes / emits a new value. For sample usage see the produceState documentation. (##) Example Here is an example of lint warnings produced by this check: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~text src/androidx/compose/runtime/foo/test.kt:8:Error: produceState calls should assign value inside the producer lambda [ProduceStateDoesNotAssignValue] produceState(true, true) { ------------ src/androidx/compose/runtime/foo/test.kt:12:Error: produceState calls should assign value inside the producer lambda [ProduceStateDoesNotAssignValue] produceState(true, true) { ------------ src/androidx/compose/runtime/foo/test.kt:17:Error: produceState calls should assign value inside the producer lambda [ProduceStateDoesNotAssignValue] produceState(true, true) { ------------ src/androidx/compose/runtime/foo/test.kt:21:Error: produceState calls should assign value inside the producer lambda [ProduceStateDoesNotAssignValue] produceState(true, true) { ------------ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Here is the source file referenced above: `src/androidx/compose/runtime/foo/test.kt`: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~kotlin linenumbers package androidx.compose.runtime.foo import androidx.compose.runtime.* @Composable fun Test() { produceState(true, true) { // Reading, not assigning the value, so this should be an error val foo = value } produceState(true, true) { // This method is a member of ProduceStateScope, so we know that it isn't // going to assign value for us awaitDispose { } } produceState(true, true) { // Receiver type of State, so assigning value is not possible doSomethingWithState() } produceState(true, true) { // Parameter type of State, so assigning value is not possible doSomethingElseWithState(this) } } fun State.doSomethingWithState() {} fun doSomethingElseWithState(state: State) {} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You can also visit the [source code](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:/compose/runtime/runtime-lint/src/test/java/androidx/compose/runtime/lint/ProduceStateDetectorTest.kt) for the unit tests for this check to see additional scenarios. The above example was automatically extracted from the first unit test found for this lint check, `ProduceStateDetector.errors`. To report a problem with this extracted sample, visit https://issuetracker.google.com/issues/new?component=612128. (##) Including !!! This is not a built-in check. To include it, add the below dependency to your project. ``` // build.gradle.kts implementation("androidx.compose.runtime:runtime-android:1.9.0-alpha01") // build.gradle implementation 'androidx.compose.runtime:runtime-android:1.9.0-alpha01' // build.gradle.kts with version catalogs: implementation(libs.runtime.android) # libs.versions.toml [versions] runtime-android = "1.9.0-alpha01" [libraries] # For clarity and text wrapping purposes the following declaration is # shown split up across lines, but in TOML it needs to be on a single # line (see https://github.com/toml-lang/toml/issues/516) so adjust # when pasting into libs.versions.toml: runtime-android = { module = "androidx.compose.runtime:runtime-android", version.ref = "runtime-android" } ``` 1.9.0-alpha01 is the version this documentation was generated from; there may be newer versions available. NOTE: These lint checks are **also** made available separate from the main library. You can also use `androidx.compose.runtime:runtime-lint:1.9.0-alpha01`. [Additional details about androidx.compose.runtime:runtime-android](androidx_compose_runtime_runtime-android.md.html). (##) Suppressing You can suppress false positives using one of the following mechanisms: * Using a suppression annotation like this on the enclosing element: ```kt // Kotlin @Suppress("ProduceStateDoesNotAssignValue") fun method() { produceState(...) } ``` or ```java // Java @SuppressWarnings("ProduceStateDoesNotAssignValue") void method() { produceState(...); } ``` * Using a suppression comment like this on the line above: ```kt //noinspection ProduceStateDoesNotAssignValue problematicStatement() ``` * Using a special `lint.xml` file in the source tree which turns off the check in that folder and any sub folder. A simple file might look like this: ```xml <?xml version="1.0" encoding="UTF-8"?> <lint> <issue id="ProduceStateDoesNotAssignValue" severity="ignore" /> </lint> ``` Instead of `ignore` you can also change the severity here, for example from `error` to `warning`. You can find additional documentation on how to filter issues by path, regular expression and so on [here](https://googlesamples.github.io/android-custom-lint-rules/usage/lintxml.md.html). * In Gradle projects, using the DSL syntax to configure lint. For example, you can use something like ```gradle lintOptions { disable 'ProduceStateDoesNotAssignValue' } ``` In Android projects this should be nested inside an `android { }` block. * For manual invocations of `lint`, using the `--ignore` flag: ``` $ lint --ignore ProduceStateDoesNotAssignValue ...` ``` * Last, but not least, using baselines, as discussed [here](https://googlesamples.github.io/android-custom-lint-rules/usage/baselines.md.html).