Assigned
Status Update
Comments
el...@google.com <el...@google.com> #2
My dependencies:
implementation 'androidx.appcompat:appcompat:1.4.0'
implementation 'androidx.preference:preference:1.1.1'
implementation 'com.google.android.gms:play-services-wearable:17.1.0'
implementation 'com.google.android.material:material:1.4.0'
If I remove androidx.appcompat:appcompat:1.4.0
, the warning vanishes, so I imagine there's some transitive dependency on an older version of androidx.appcompat:appcompat
that doesn't have the warning.
el...@google.com <el...@google.com> #4
The upstream library is using @SuppressWarnings("deprecation")
, which I suppose you could probably use to suppress the warning you're getting.
As for doing fully the non-deprecated way, it is possible that would require overwriting/duplicating more functionality than you currently are and/or updates to the Preference library.
However, I suspect that FragmentManager is capable of handling Fragment subclasses. You should probably look for instructions on developer.android.com, stackoverflow, or similar.
Description
DataStore Version used: 1.0.0
While data being read/write from the datastore, if the scope get cancelled, Cancellation exception being thrown.
Example code look like this
```
val scope = CoroutineScope(SupervisorJob() + Dispatchers.IO)
val datastore = PreferenceDataStoreFactory.create(scope = scope) {
produceFile()
}
repeat(10) { count ->
runBlocking {
val value = datastore.data.map {
it[stringPreferencesKey("test_key_$count")]
}.first()
println(value)
if (count == 3) {
scope.cancel()
}
}
}
```
In the above code, fist 4 values being read and then throw the exception.
As I see in the code (SimpleActor), ongoing operations will not be interrupted and handle in invokeOnComplete, but error will be thrown from messageQueue
Is this intentional behaviour?