Status Update
Comments
mg...@google.com <mg...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Hao Dong <
Link:
Update documentation and annotations
Expand for full commit details
Update documentation and annotations
1. Update BiometricPrompt documentation with strength info
2. Add @Deprecated annotation for IdentityCredential to keep
consistent with framework.
3. Use rule instead of MockitoAnnotations
Fixes: 140252778
Fixes: 217942278
Fixes: 251211046
Fixes: 239955609
Relnote: "Add @Deprecated annotation for IdentityCredential to keep
consistent with framework."
Test: ./gradlew biometric:biometric:assemble
Test: ./gradlew biometric:biometric:updateApi
Change-Id: I6ac906032150503829af6a4aca028037be7934af
Files:
- M
biometric/biometric/api/current.txt
- M
biometric/biometric/api/restricted_current.txt
- M
biometric/biometric/lint-baseline.xml
- M
biometric/biometric/src/androidTest/java/androidx/biometric/DeviceUtilsTest.java
- M
biometric/biometric/src/main/java/androidx/biometric/BiometricPrompt.java
- M
biometric/biometric/src/main/java/androidx/biometric/CryptoObjectUtils.java
- M
biometric/biometric/src/test/java/androidx/biometric/AuthenticationCallbackProviderTest.java
- M
biometric/biometric/src/test/java/androidx/biometric/BiometricManagerTest.java
- M
biometric/biometric/src/test/java/androidx/biometric/CancellationSignalProviderTest.java
- M
biometric/biometric/src/test/java/androidx/biometric/CryptoObjectUtilsTest.java
- M
biometric/biometric/src/test/java/androidx/biometric/KeyguardUtilsTest.java
- M
biometric/biometric/src/test/java/androidx/biometric/PackageUtilsTest.java
- M
credentials/credentials/src/main/java/androidx/credentials/provider/utils/CryptoObjectUtils.kt
Hash: 65b837ca1bbe66dafeab43b78bca416d6abc04fc
Date: Tue Nov 12 18:27:57 2024
ap...@google.com <ap...@google.com> #3
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.credentials:credentials:1.5.0-rc01
ap...@google.com <ap...@google.com> #4
Project: platform/frameworks/support
Branch: androidx-main
Author: Marcello Galhardo <
Link:
Move KMP compatible test dependencies to commonTest
Expand for full commit details
Move KMP compatible test dependencies to `commonTest`
Test: N/A
Bug: 378895074
Change-Id: I77d03d1da41808e03d5e2978b768dc3ef6649211
Files:
- M
lifecycle/lifecycle-viewmodel-compose/build.gradle
Hash: e266fa197c54fe55955b2de9acc1c1d9894e6376
Date: Fri Jan 17 14:25:48 2025
mg...@google.com <mg...@google.com>
ap...@google.com <ap...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-main
Author: Marcello Galhardo <
Link:
Move MutableStateSerializer
to savedstate-compose
Expand for full commit details
Move `MutableStateSerializer` to `savedstate-compose`
- This change moves `MutableStateSerializer` from `lifecycle-viewmodel-compose` to `savedstate-compose`. This corrects its previous misplacement and aligns with the design outlined in go/savedstate-compose, which specifies that all `savedstate-compose` related APIs should reside within the `savedstate-compose` module.
RelNote: "Move `MutableStateSerializer` to `savedstate-compose`."
Test: MutableStateSerializerTest
Bug: 378895074
Change-Id: I4f690e41dc5619d185784409170943abeb0f0550
Files:
- M
lifecycle/lifecycle-viewmodel-compose/api/current.txt
- M
lifecycle/lifecycle-viewmodel-compose/api/restricted_current.txt
- M
savedstate/savedstate-compose/api/current.txt
- M
savedstate/savedstate-compose/api/restricted_current.txt
- M
savedstate/savedstate-compose/src/androidInstrumentedTest/kotlin/androidx/savedstate/compose/serialization/serializers/MutableStateSerializerTest.android.kt
- M
savedstate/savedstate-compose/src/commonMain/kotlin/androidx/savedstate/compose/serialization/serializers/MutableStateSerializer.kt
Hash: f845eabb6c5e3b138059839e59f383f70304d792
Date: Wed Jan 29 11:31:04 2025
pr...@google.com <pr...@google.com> #6
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.lifecycle:lifecycle-viewmodel-compose:2.9.0-alpha10
androidx.lifecycle:lifecycle-viewmodel-compose-android:2.9.0-alpha10
androidx.lifecycle:lifecycle-viewmodel-compose-desktop:2.9.0-alpha10
androidx.savedstate:savedstate-compose:1.3.0-alpha08
androidx.savedstate:savedstate-compose-android:1.3.0-alpha08
androidx.savedstate:savedstate-compose-jvmstubs:1.3.0-alpha08
androidx.savedstate:savedstate-compose-linuxx64stubs:1.3.0-alpha08
Description
saveable
has built-in support for Compose'sMutableState
, supporting this use case:It does this by providing an overloaded function that handles
MutableState.value
and serializes it when needed.To help people migrate from
saveable
tosaved
, we want to supportMutableState
in our KotlinX serialization support.While working on
getMutableState
, I experimented with this and created a naiveKSerializer
implementation to handleMutableState
.Here’s what it could look like:
For serialization, we'd use
(value as MutableState<T>).value
+valueSerializer
to serialize the content. Deserialization works in the opposite direction.Here’s a usage example:
However, calling this without the serializer would cause an exception.
Our variant should work like
saveable
: ifT
(the generic type insaved
) is serializable, it should work without needing the serializer.The goal is to find the best way to support
MutableState
insaved
(using aKSerializer
, overloads, or another method).Related to b/378895070 .