Obsolete
Status Update
Comments
mb...@gmail.com <mb...@gmail.com> #2
Related to
uc...@google.com <uc...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-main
Author: Marcello Galhardo <
Link:
Add MutableStateFlowSerializer
for serializing MutableState
Expand for full commit details
Add `MutableStateFlowSerializer` for serializing `MutableState`
- Introduced an inline `MutableStateFlowSerializer` function to infer and retrieve the appropriate `KSerializer` for `MutableStateFlow` of a serializable type.
- Added an overload of `MutableStateFlowSerializer` that accepts an explicit `KSerializer` for the wrapped type, allowing for customizing the `KSerializer`.
- Implemented `MutableStateFlowSerializerImpl`, a private class that handles the serialization and deserialization logic for `MutableStateFlow`, delegating inner value processing to the provided `KSerializer`.
- Only `KSerializer<MutableStateFlow<T>>` is exposed; the `MutableStateFlowSerializerImpl` remains private.
RelNote: "Add `MutableStateFlowSerializer` for serializing `kotlinx.coroutines.flow.MutableStateFlow`."
Test: MutableStateFlowSerializerTest.kt
Fixes: 378895070
Change-Id: I6a8925772d2f124d2db4a83bff0062c1db0eb0fb
Files:
- M
savedstate/savedstate/api/current.txt
- M
savedstate/savedstate/api/restricted_current.txt
- M
savedstate/savedstate/bcv/native/current.txt
- M
savedstate/savedstate/build.gradle
- A
savedstate/savedstate/src/commonMain/kotlin/androidx/savedstate/serialization/serializers/MutableStateFlowSerializer.kt
- A
savedstate/savedstate/src/commonTest/kotlin/androidx/savedstate/serialization/MutableStateFlowSerializerTest.kt
Hash: 3f45907910984f32745d62d9846e7083a3c75e4a
Date: Mon Jan 20 12:32:07 2025
mb...@gmail.com <mb...@gmail.com> #4
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.savedstate:savedstate:1.3.0-alpha07
androidx.savedstate:savedstate-android:1.3.0-alpha07
androidx.savedstate:savedstate-desktop:1.3.0-alpha07
androidx.savedstate:savedstate-iosarm64:1.3.0-alpha07
androidx.savedstate:savedstate-iossimulatorarm64:1.3.0-alpha07
androidx.savedstate:savedstate-iosx64:1.3.0-alpha07
androidx.savedstate:savedstate-linuxarm64:1.3.0-alpha07
androidx.savedstate:savedstate-linuxx64:1.3.0-alpha07
androidx.savedstate:savedstate-macosarm64:1.3.0-alpha07
androidx.savedstate:savedstate-macosx64:1.3.0-alpha07
uc...@google.com <uc...@google.com> #5
can you do a clean project or Invalidate caches and let us know the feedback.
mb...@gmail.com <mb...@gmail.com> #6
Tried both - invalidate caches plus a new, clean project
Same effect.
Two INVALID markers when searching for parent" (only with a " at the end so i find "parent" and "match_parent" for multiple hits)
Double clicked the first match - Ctrl-X --> two INVALID markers.
Same effect.
Two INVALID markers when searching for parent" (only with a " at the end so i find "parent" and "match_parent" for multiple hits)
Double clicked the first match - Ctrl-X --> two INVALID markers.
uc...@google.com <uc...@google.com> #7
Ok , reproduce same issue and then share idea.log file
mb...@gmail.com <mb...@gmail.com> #8
Hi again
ok I repeated my experiment from yesterday - still same behavior.
I attached the idea.log for today.
Hope this helps (I personally couldn't see anything bad in it, but I am no pro in interpreting idea log)
ok I repeated my experiment from yesterday - still same behavior.
I attached the idea.log for today.
Hope this helps (I personally couldn't see anything bad in it, but I am no pro in interpreting idea log)
uc...@google.com <uc...@google.com> #9
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
rp...@google.com <rp...@google.com>
mb...@gmail.com <mb...@gmail.com> #10
Hello out there,
I'd like to update this issue: The bug is gone with Studio 3.2
I can no longer reproduce this behavior, so this issue may be closed.
Thank you
Cheers
I'd like to update this issue: The bug is gone with Studio 3.2
I can no longer reproduce this behavior, so this issue may be closed.
Thank you
Cheers
Description
AI-171.4408382, JRE 1.8.0_152-release-915-b01x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080
IMPORTANT: Please read
Gradle Version: 4.1
Android Plugin Version: 3.0.0
TargetSDK (compiledSDK): 27
MinSDK: 21
Build Tools Version: 27.0.0 (latest - using default setting which points to latest installed)
Android SDK Tools: 26.1.1
How to reproduce:
* Hit Shift-Ctrl-F and search for something, that has more than one hit in a file and click "View in Find window" on the bottom right
* follow the click order in the screenshot - make sure, you delete a line, that really has only ONE hit of the searched term (in the screenshot I used a search pattern of an entire line to avoid a false positive)
(You understand the following lines after you tried what is shown in the screenshot):
* You can click that second "INVALID" line and it *will* find an occurrence in the code, so the "INVALID" is... well invalid :) it should still show an occurrence.
kind regards