Assigned
Status Update
Comments
st...@gmail.com <st...@gmail.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.
Description
DataStore Component used: N/A
DataStore Version used: N/A
Devices/Android versions reproduced on: N/A
The documentation DataStore in developer.android.com does not have any section on how a migration should be done when not going from SharedPreferences -> Datastore, but simply from having Datastore and wanting to do some backwards incompatible changes.
Even this blogpost from Google shows how one would do this by creating a brand new datastore file which isn't what I'd expect one would do since it could eventually blow up to way too many datastore instances existing. Aside from that, it shows
override suspend fun shouldMigrate(currentData: Preferences) = true
which I assume will trigger the migration all the time, which feels like is the wrong thing to do, no?If I am missing some part of the documentation or some samples inhttps://cs.android.com/ please do point me to them if you would be so kind.