IssueTracker

Jetpack Compose compiler version: 1.5.4 Android Studio Build: #AI-223.8836.35.2231.11090377, built on November 13, 2023 Kotlin version: 1.9.20

The change introduced by commit 22421ef1f3aab2bb317e164845bf1630606a099c uses currentFile.fileEntry.name field to generate keys to be passed to startReplaceableGroup call. I discovered that this field contains the absolute file path, not just the part relative to the project root.

In practice that results in binary different artifacts being produced for binary equivalent sources stored under different paths. E.g. builds under /tmp/ci-build-42/ will always produce binary equal artifacts for a given source code revision, but these artifacts will be different from the ones produced from the same revision under /tmp/ci-build-43/.

Steps to Reproduce or Code Sample to Reproduce:

1. Create a new project with "Empty Activity" template
2. Set the Compose compiler version to 1.5.4 and Kotlin plugin to 1.9.20
3. Build the application using ./gradlew clean build --no-daemon, store ./app/build/intermediates/compile_app_classes_jar/release/classes.jar
4. Copy the project root somewhere else
5. Rebuild the application again with the same command under the new root, store the same file
6. Compare files from two builds from different directories

ReproducerComposableKt.class will be the only file different between the resulting jars. By applying javap -c and comparing the output for these classes, you'll see the only difference there is a value for a constant used in startReplaceableGroup call.

For your convenience I also provide projects for compiler versions 1.5.4 and 1.5.3 I used to verify my findings (see reproducer.tgz). Also, the fileName value I extracted with a debugger from 1.5.4 project looks like this:

_Users_My_Name_AndroidStudioProjects_ComposeReproIssueReproducer_1_5_4_app_src_main_java_com_example_composereproissuereproducer_ReproducerComposableKt