Status Update
Comments
ap...@google.com <ap...@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.
yb...@google.com <yb...@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.
yb...@google.com <yb...@google.com> #5
Looks like a duplicate of
Description
Once we allow multiple instances of a DS for the same file, the test can be fixed not to do that and then we should make storageConnection private again.