IssueTracker

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.

https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:preference/preference/src/main/java/androidx/preference/PreferenceDialogFragmentCompat.java;l=53;drc=ca9feb3b73769089afbfd36b4d4a3d91239f9cd5;bpv=1;bpt=0

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.

Looks like a duplicate of https://issuetracker.google.com/issues/181793702, ow...@google.com I proposed a "solution" to this in the other issue.

This target is "enabled" in AndroidX now, but the support level is basically non-existent. We are still working on getting CI, so we cannot make any guarantees about the stability of mingw artifacts even if we did release them.

Re-assigning back to datastore folks so they can decide on timeline.

Created aosp/3209641 but it fails compilations. I fixed the dependency issue from annotation but kruth seems to block:

Could not determine the dependencies of task ':datastore:datastore:linkDebugTestMingwX64'.
> Could not resolve all dependencies for configuration ':datastore:datastore:mingwX64TestCompileKlibraries'.
   > Could not resolve project :kruth:kruth.
     Required by:
         project :datastore:datastore
      > No matching variant of project :kruth:kruth was found. The consumer was configured to find a library for use during 'kotlin-api', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.native.target' with value 'mingw_x64', attribute 'org.jetbrains.kotlin.platform.type' with value 'native' but:

It seems kruth:kruth doesn't support windows yet.

Is there a plan from Jetpack to support kruth on windows?

You should be able to just add mingwX64() to kruth, it is largely platfrom independent source code there.

Thanks, created aosp/3217077 for kruth.

Now that Kruth supports mingwX64, could mingwX64 be added to datastore as well, please? Thanks for working on this. I am currently using my own simple implementation for writing some data to a file, but would really like to use datastore instead.

Hi thanks for your interest #comment11. Per my earlier discussion with infrastructure team, we do not have Windows machines to run the CI tests, so it may be hard for us to ensure the released artifact is behaving correctly, so we put the efforts on hold.

I'm not sure what's the timeline for Jetpack infra team to support Windows environment for CI tests.

Can you employ a tier system similar to JetBrains?

https://kotlinlang.org/docs/native-target-support.html

There's really no downside to publishing "pure" Kotlin libraries to all possible targets even if they are untested. It's only when you interact with platform APIs or have native dependencies that things get complicated.

Re #13 We do already have a very similar tiers of support https://developer.android.com/kotlin/multiplatform#supported-platforms