Fixed
Status Update
No update yet.
Comments
ap...@google.com
I think that ResultReceiver will "forever" stay in the old package since otherwise it would be a breaking AIDL-related change.
ap...@google.com
Yep, it has to stay in the old package.
> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"
Config issue.
> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"
Config issue.
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Author: Filip Pavlis <pavlis@google.com>
Date: Tue Feb 12 19:41:53 2019
Revert changes in default.config and remove task.
It turned out that we have released (as part of beta03) mappings that
were not supposed to be used externally. This is because we were actively
maintaining "dejetifyArchive" task without realizing that next jetifier
update will contain such changes. As we are done with 28.0.0 I think it
is a good time to sunset the "dejetifyArchive" target. I also reverted
all the config changes that are not supposed to go outside. Please note
that there is still "partiallyDejetifyArchive" for migration purpouses
and is still part of continuous build.
Also added ignore rule for ResultReceiver.
Bug:
Bug:
Test: N/A
Change-Id: I59983d25ae7e0939f2e9e54005460ad0f73beb3c
M buildSrc/jetify.gradle
M buildSrc/src/main/kotlin/androidx/build/AndroidXPlugin.kt
M buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M jetifier/jetifier/core/src/main/resources/default.config
M jetifier/jetifier/core/src/main/resources/default.generated.config
https://android-review.googlesource.com/902433
https://goto.google.com/android-sha1/2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Branch: androidx-master-dev
commit 2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Author: Filip Pavlis <pavlis@google.com>
Date: Tue Feb 12 19:41:53 2019
Revert changes in default.config and remove task.
It turned out that we have released (as part of beta03) mappings that
were not supposed to be used externally. This is because we were actively
maintaining "dejetifyArchive" task without realizing that next jetifier
update will contain such changes. As we are done with 28.0.0 I think it
is a good time to sunset the "dejetifyArchive" target. I also reverted
all the config changes that are not supposed to go outside. Please note
that there is still "partiallyDejetifyArchive" for migration purpouses
and is still part of continuous build.
Also added ignore rule for ResultReceiver.
Bug:
Bug:
Test: N/A
Change-Id: I59983d25ae7e0939f2e9e54005460ad0f73beb3c
M buildSrc/jetify.gradle
M buildSrc/src/main/kotlin/androidx/build/AndroidXPlugin.kt
M buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M jetifier/jetifier/core/src/main/resources/default.config
M jetifier/jetifier/core/src/main/resources/default.generated.config
ap...@google.com
FYI, in AGP 3.4.0-rc03 and 3.5.0-alpha09, the AGP has been updated to use Jetifier 1.0.0-beta04, which should have the fix for the above issue: https://android.googlesource.com/platform/tools/base/+/f7fdfbb94aebb43b7e9515c683fd71b8c905ee79 .
ap...@google.com
Closing as fixed.
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit aad31661faf4f14036a23a5d0b73147dda032094
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:45:05 2022
Add project dependency constraint between lifecycle-reactivestreams and lifecycle-reactivestreams-ktx
Added bi-directional project version constraint between
lifecycle-reactivestreams and lifecycle-reactivestreams-ktx.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I8e39eed1d37def3dcc3aa38ef1f4edd1583f40c1
M lifecycle/lifecycle-reactivestreams/build.gradle
M lifecycle/lifecycle-reactivestreams-ktx/build.gradle
https://android-review.googlesource.com/2189943
Branch: androidx-main
commit aad31661faf4f14036a23a5d0b73147dda032094
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:45:05 2022
Add project dependency constraint between lifecycle-reactivestreams and lifecycle-reactivestreams-ktx
Added bi-directional project version constraint between
lifecycle-reactivestreams and lifecycle-reactivestreams-ktx.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I8e39eed1d37def3dcc3aa38ef1f4edd1583f40c1
M lifecycle/lifecycle-reactivestreams/build.gradle
M lifecycle/lifecycle-reactivestreams-ktx/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit f83ce34e8fddb3eb499f98c1262c346d11ee0205
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:28:49 2022
Add project dependency constraint between lifecycle-livedata and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-lifedata and lifecycle-livedata-core. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I3e67cbe8fa8bbc3999f0f463f22b484ea66ba988
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-livedata/build.gradle
https://android-review.googlesource.com/2189937
Branch: androidx-main
commit f83ce34e8fddb3eb499f98c1262c346d11ee0205
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:28:49 2022
Add project dependency constraint between lifecycle-livedata and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-lifedata and lifecycle-livedata-core. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I3e67cbe8fa8bbc3999f0f463f22b484ea66ba988
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-livedata/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit fe17ed80e60d5ec3bb42fe0552415424b7b3dde5
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:36:11 2022
Add project dependency constraint between lifecycle-livedata and lifecycle-livedata-ktx
Added bi-directional project version constraint between
lifecycle-lifedata and lifecycle-livedata-ktx. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: Iba6d1ffb952fd20be91b813dcac193ecc1776173
M lifecycle/lifecycle-livedata-ktx/build.gradle
M lifecycle/lifecycle-livedata/build.gradle
https://android-review.googlesource.com/2189940
Branch: androidx-main
commit fe17ed80e60d5ec3bb42fe0552415424b7b3dde5
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:36:11 2022
Add project dependency constraint between lifecycle-livedata and lifecycle-livedata-ktx
Added bi-directional project version constraint between
lifecycle-lifedata and lifecycle-livedata-ktx. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: Iba6d1ffb952fd20be91b813dcac193ecc1776173
M lifecycle/lifecycle-livedata-ktx/build.gradle
M lifecycle/lifecycle-livedata/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 1e948aed8d0c01823ae60258ade0694da728b36d
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:40:29 2022
Add project dependency constraint between lifecycle-livedata-core and lifecycle-livedata-core-ktx
Added bi-directional project version constraint between
lifecycle-lifedata-core and lifecycle-livedata-core-ktx.
If both artifacts are in the dependency tree, their
versions should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I6c6dd9de2e252217095c60de8ef577be6d940f1a
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-livedata-core-ktx/build.gradle
https://android-review.googlesource.com/2189941
Branch: androidx-main
commit 1e948aed8d0c01823ae60258ade0694da728b36d
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 17:40:29 2022
Add project dependency constraint between lifecycle-livedata-core and lifecycle-livedata-core-ktx
Added bi-directional project version constraint between
lifecycle-lifedata-core and lifecycle-livedata-core-ktx.
If both artifacts are in the dependency tree, their
versions should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I6c6dd9de2e252217095c60de8ef577be6d940f1a
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-livedata-core-ktx/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 325aa99d830327ccf016231f9836cf04db65c3ff
Author: Sanura N'Jaka <sanura@google.com>
Date: Mon Aug 22 22:23:18 2022
Add project dependency constraint between lifecycle-common and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-common and lifecycle-livedata-core. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I22e0fda00e22bc4fc56ac1bf5b7dcd2369ad533e
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-common/build.gradle
https://android-review.googlesource.com/2192537
Branch: androidx-main
commit 325aa99d830327ccf016231f9836cf04db65c3ff
Author: Sanura N'Jaka <sanura@google.com>
Date: Mon Aug 22 22:23:18 2022
Add project dependency constraint between lifecycle-common and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-common and lifecycle-livedata-core. If both
artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle
automatically bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I22e0fda00e22bc4fc56ac1bf5b7dcd2369ad533e
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-common/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 27355f7c30e816f6636928caeef29d473b896e28
Author: Sanura N'Jaka <sanura@google.com>
Date: Wed Aug 24 22:41:48 2022
Add project dependency constraint between lifecycle-viewmodel-savedstate and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-viewmodel-savedstate and lifecycle-livedata-core.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle automatically
bumping up either version to meet constraint.
Test: N/A
Fixes: 242871265
Change-Id: I94cc3ddd0f86033653c1477cf3f8ad8a1d93adae
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-viewmodel-savedstate/build.gradle
https://android-review.googlesource.com/2193733
Branch: androidx-main
commit 27355f7c30e816f6636928caeef29d473b896e28
Author: Sanura N'Jaka <sanura@google.com>
Date: Wed Aug 24 22:41:48 2022
Add project dependency constraint between lifecycle-viewmodel-savedstate and lifecycle-livedata-core
Added bi-directional project version constraint between
lifecycle-viewmodel-savedstate and lifecycle-livedata-core.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle automatically
bumping up either version to meet constraint.
Test: N/A
Fixes: 242871265
Change-Id: I94cc3ddd0f86033653c1477cf3f8ad8a1d93adae
M lifecycle/lifecycle-livedata-core/build.gradle
M lifecycle/lifecycle-viewmodel-savedstate/build.gradle
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit 0598f5400a797fc9e31858e0d8a1b575ad7158a7
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 18:28:20 2022
Add project dependency constraint between lifecycle-viewmodel-savedstate and lifecycle-viewmodel-compose
Added bi-directional project version constraint between
lifecycle-viewmodel-savedstate and lifecycle-viewmodel-compose.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle automatically
bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I2810d3afbe0cb8e8e387d1bc64eb3c698285d471
M lifecycle/lifecycle-viewmodel-savedstate/build.gradle
M lifecycle/lifecycle-viewmodel-compose/build.gradle
https://android-review.googlesource.com/2190016
Branch: androidx-main
commit 0598f5400a797fc9e31858e0d8a1b575ad7158a7
Author: Sanura N'Jaka <sanura@google.com>
Date: Thu Aug 18 18:28:20 2022
Add project dependency constraint between lifecycle-viewmodel-savedstate and lifecycle-viewmodel-compose
Added bi-directional project version constraint between
lifecycle-viewmodel-savedstate and lifecycle-viewmodel-compose.
If both artifacts are in the dependency tree, their versions
should match. This will now be enforced by gradle automatically
bumping up either version to meet constraint.
Test: N/A
Bug: 242871265
Change-Id: I2810d3afbe0cb8e8e387d1bc64eb3c698285d471
M lifecycle/lifecycle-viewmodel-savedstate/build.gradle
M lifecycle/lifecycle-viewmodel-compose/build.gradle
na...@google.com
This bug was linked in a change in the following release(s):
androidx.lifecycle:lifecycle-common:2.6.0-alpha02androidx.lifecycle:lifecycle-livedata:2.6.0-alpha02androidx.lifecycle:lifecycle-livedata-core:2.6.0-alpha02androidx.lifecycle:lifecycle-livedata-core-ktx:2.6.0-alpha02androidx.lifecycle:lifecycle-livedata-ktx:2.6.0-alpha02androidx.lifecycle:lifecycle-reactivestreams:2.6.0-alpha02androidx.lifecycle:lifecycle-reactivestreams-ktx:2.6.0-alpha02androidx.lifecycle:lifecycle-runtime:2.6.0-alpha02androidx.lifecycle:lifecycle-runtime-compose:2.6.0-alpha02androidx.lifecycle:lifecycle-runtime-ktx:2.6.0-alpha02androidx.lifecycle:lifecycle-runtime-testing:2.6.0-alpha02androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02androidx.lifecycle:lifecycle-viewmodel-compose:2.6.0-alpha02androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.0-alpha02androidx.lifecycle:lifecycle-viewmodel-savedstate:2.6.0-alpha02
da...@google.com
This release seems to have conflicting artifacts in the classpath. When both:
androidx.lifecycle:lifecycle-viewmodel-ktx:2.6.0-alpha02
androidx-lifecycle:lifecycle-livedata-ktx:2.6.0-alpha02
are added as dependencies, the following error pops up:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':sync:sync-test:checkProdDebugAndroidTestDuplicateClasses'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
> Duplicate class androidx.lifecycle.ViewModelLazy found in modules lifecycle-viewmodel-2.6.0-alpha02-runtime (androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02) and lifecycle-viewmodel-ktx-2.3.1-runtime (androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1)
Duplicate class androidx.lifecycle.ViewTreeViewModelKt found in modules lifecycle-viewmodel-2.6.0-alpha02-runtime (androidx.lifecycle:lifecycle-viewmodel:2.6.0-alpha02) and lifecycle-viewmodel-ktx-2.3.1-runtime (androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1)
Go to the documentation to learn how to <a href="d.android.com/r/tools/classpath-sync-errors">Fix dependency resolution errors</a>.
Downgrading to 2.6.0-alpha01 fixes this.
sa...@google.com
As an update to the above comment from TJ, this issue has been fixed and will be available in Lifecycle 2.6.0-alpha03.
na...@google.com
The following release(s) address this bug:
androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03androidx.lifecycle:lifecycle-runtime-compose:2.6.0-alpha03androidx.lifecycle:lifecycle-viewmodel-compose:2.6.0-alpha03androidx.lifecycle:lifecycle-viewmodel-savedstate:2.6.0-alpha03
Description
Component used: Lifecycle
Version used: 2.6.0-alpha01
Until feature requests such as
lifecycle-common:2.6.0-alpha01withlifecycle-runtime:2.5.1).Gradle supports
We should manually add two way constraints, similarly to what was done for Paging in
The pairs of artifacts we should add constraints to should match the dependencies we have right now, which should mean the list looks something like: