IssueTracker

ViewModelProviderKt exists in both lifecycle-viewmodel-ktx:2.3.1, which gets pulled in transitively by appcompat, and lifecycle-viewmodel at head. If I update appcompat to lifecycle-viewmodel it's going to cause a classpath conflict for a lot of external clients.

Dependency constraints should be used here, but Gradle has several bugs in dependency constraint resolution that prevent us from using it (see https://github.com/gradle/gradle/issues/19882).

Type androidx.lifecycle.ViewModelProviderKt is defined multiple times: $OUT_DIR/androidx/lifecycle/lifecycle-viewmodel/build/.transforms/0f7639188e2c092b20b9a0a66b44635c/transformed/classes/classes.dex, $OUT_DIR/androidx/support-preference-demos/build/intermediates/external_libs_dex/release/mergeExtDexRelease/classes.dex

Please use a different JvmName for the class in lifecycle-viewmodel so that we can avoid the conflict without needing to block lifecycle-viewmodel or appcompat's release on Gradle fixing their bugs.