Status Update
No update yet.
Comments
sa...@gmail.com
so...@google.com
so...@google.com
Triage notes: Assigning for a response.
tj...@gmail.com
When updating the providers, startProvider() is comparing the new scope produces with the previous scope produced, instead of the current parent scope, to determine if the content of the provider needs to change, ignoring if the parent changed. That has the effect of, if a provider provides a value that is identical to the parent value, the composer thinks that none of the the static composition locals changed and it doesn't need to force updates of the content of the provider.
The temporary work-around for this is to use a compositionLocalOf instead. Using compositionLocalOf is recommended for composition locals that can change and static should are not recommended for values that can change.
However, in the above example, LocalOtherValue only changes once so using a staticCompositionLocal is recommended as it avoids the overhead for tracking reads of a value that rarely changes, making this work-around temporary for LocalOtherValue or similar locals.
fe...@gmail.com
ko...@gmail.com
This issue also affects Material theming changes because they use staticCompositionLocalOf under the hood. And those cannot be changed by a work-around.
pi...@gmail.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Chuck Jazdzewski <
Link:
Fixed providesDefault for a single provide
Expand for full commit details
Fixed `providesDefault` for a single provide
If `providesDefault` is used as the sole provided value
of a `CompostionLocalProvider` then the content of the
provider may not update if a parent changes the value
of a static composition local. Providing more than
one value does not have this issue.
Fixes: 374263387
Test: new test, ./gradlew :compose:r:r:test
Change-Id: Iabd4fbba6191abad4073ab5f302d252750683258
Files:
- M
compose/runtime/runtime/src/commonMain/kotlin/androidx/compose/runtime/Composer.kt - M
compose/runtime/runtime/src/nonEmulatorCommonTest/kotlin/androidx/compose/runtime/CompositionLocalTests.kt
Hash: b70a4268ba4985d4a5baf9c14edd81290d2ded1d
Date: Thu Oct 24 17:16:39 2024
st...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.runtime:runtime:1.8.0-alpha06androidx.compose.runtime:runtime-android:1.8.0-alpha06androidx.compose.runtime:runtime-jvmstubs:1.8.0-alpha06androidx.compose.runtime:runtime-linuxx64stubs:1.8.0-alpha06
pi...@gmail.com
OS version UQ1A.240105.002
Description
- Build Number: google/bluejay_beta/bluejay:14/U1B2.230922.006/10879723:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Google Assistant / Search
When did this happen?
Oct 6, 2023 1:07 PM GMT+05:30
What steps would let us observe this issue?
1. Open settings then apps then assistant then hey Google and voice match
What did you expect to happen?
Hey Google should work
What actually happened?
It is not available for me
How often has this happened?
Once
What was the effect of this issue on your device usage, such as lost time or work?
Moderate
Debugging information
Google Play services
com.google.android.gms
Version 233758044 (23.37.58 (190400-570425155))
System App (Updated)
Android System WebView
com.google.android.webview
Version 593814031 (117.0.5938.140)
System App (Updated)
Network operator: Jio True5G
SIM operator: Jio
Filed by Android Beta Feedback. Version (Updated): 2.37-betterbug.external_20230817_RC02 (DOGFOOD)
To learn more about our feedback process, please visit