IssueTracker

What version of kotlin are you using?

1.7.10

related b/266687218

Fixed by https://cs.android.com/android-studio/platform/tools/base/+/2553f154c9148529f7bdad459553ca33fffd38d2 for the next canary.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Iguana | 2023.2.1 Canary 6
• Android Gradle Plugin 8.3.0-alpha06

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Hung, kicking to you initially in case this is a Gradle change you're aware of. Kick back to me if you have no idea what is going on here, and I'll escalate locally.

i'm looking into reproducing it. we do have tests where adapters from sub modules are used so it is scary how this got missed. also didn't change anything in data binding :/.

i'mlooking into this in between meetings so a bit slow but initial findings:

➜  tivi git:(main) ✗ find ./common-databinding/build/intermediates/data_binding_artifact/ -name "*.json"|grep -i setter
./common-databinding/build/intermediates/data_binding_artifact/debug/app.tivi.common.databinding-setter_store.json
➜  tivi git:(main) ✗ find ./common-layouts/build/intermediates/data_binding_dependency_artifacts/ -name "*.json"|grep -i setter
./common-layouts/build/intermediates/data_binding_dependency_artifacts/debug/com.airbnb.epoxy.databinding-setter_store.json
./common-layouts/build/intermediates/data_binding_dependency_artifacts/debug/dev.chrisbanes.insetter.dbx-setter_store.json
./common-layouts/build/intermediates/data_binding_dependency_artifacts/debug/androidx.databinding.library.baseAdapters-setter_store.json

seems like setter store (the output of parsing binding adapters) is generated for common-databinding but it is not copied into the layouts project.

meanwhile, dependencies from gradle outputs are copied.

Hung, did anything change there?

also reproduces with tip of tree.

I just found that this change broke the publishing of data binding's setter store and br files: https://android.googlesource.com/platform/tools/base/+/9e60cd82495fb937089714aab61d7f74f4630cd4

I'm working on a fix.

also our mutli module test is passing so nothing is broken in the infra as well.

the difference is that, that test is in java :/. i'll try adding a kotlin module there to see if it helps reproduce.

Yup, the above change only impacts modules that use Kapt.

this reproduces the issue: https://googleplex-android-review.git.corp.google.com/c/platform/frameworks/data-binding/+/12222450

Didn't have time to debug yet.

more info:

The merge artifacts task is not seeing the artifacts provided by the dependency.

task.runtimeDependencies = creationConfig.variantDependencies.getArtifactFileCollection(
                AndroidArtifacts.ConsumedConfigType.RUNTIME_CLASSPATH,
                AndroidArtifacts.ArtifactScope.ALL,
                AndroidArtifacts.ArtifactType.DATA_BINDING_ARTIFACT
            )
            task.compileTimeDependencies = creationConfig.variantDependencies.getArtifactFileCollection(
                AndroidArtifacts.ConsumedConfigType.COMPILE_CLASSPATH,
                AndroidArtifacts.ArtifactScope.ALL,
                AndroidArtifacts.ArtifactType.DATA_BINDING_ARTIFACT
            )

the getArtifactFileCollection does not return anything from module dependencies that are in the same project.

I see some changes in that area by jedo@ but i'm not sure if any of them would trigger this.

Ivan / Hung, Jedo said you might have an idea what is broken here.

To reproduce:

checkout the CL above in tools/data-binding
cd tools/base && ./gradlew :pL :makeOfflineRepo
cd ../data-binding
./init.sh # this just makes test projects use latest gradle
cd integration-tests/KotlinTestApp
./gradlew app:connectedCheck -Pandroid.injected.invoked.from.ide=true
# invoked from ide is important, otherwise they'll assume gradle connected check runner setup

You can put a debug point on DataBindingMergeDependencyArtifactsTask and observe that the artifacts from the module do not show up.

Yup I've found the root cause (comment #11).

I've sent out a fix for review: Change-Id: I3ed5520fc33184475a42c19d19412a87cb2d386d

We have fixed this issue: https://android.googlesource.com/platform/tools/base/+/cea0b5923006a9eff4b19a4530cf496dc47da092 (the commit message explains the root cause), with a regression test to prevent this issue from reappearing.

I'm trying to cherry-pick the fix to AGP 4.2.0-alpha06, otherwise it will probably be in 4.2.0-alpha07.

Thanks a lot for the report!

The following changes were cherrypicked through Coastguard
Release Track: 5146371478454272
Changes: ag/12219788