Status Update
No update yet.
Comments
sg...@google.com
sg...@google.com
ph...@gmail.com
for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.
ra...@gmail.com
ap...@google.com
Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?
ap...@google.com
no we don't have a plan to backport this. why is this blocking you from upgrading ?
ap...@google.com
We sign apk's and bundles via internal service, and i don't know another way to interact with artifacts;
Yesterday i ended up with some ugly workaround:
ap...@google.com
I commented on the merge request but to summarize :
you can set your signing tasks output folder to wherever you need to be :
artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }
if you don't set it, then we will set a directory automatically.
ap...@google.com
Thanks, Jerome!
ap...@google.com
I checked that we do have correct behavior for FILE based artifacts like bundle :
> Task :app:debugUpdateArtifact
originalArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/bundle/debug/signDebugBundle/app-debug.aab
updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab
however, we still seem to not be consistent for the DIRECTORY based artifacts like APK:
> Task :app:debugUpdateAPKArtifact
Input folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug
Output folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/apk/debug
Input file: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug/app-debug.apk
Alex, can you have a look ?
Description
I started seeing
minifyReleaseWithR8task failure of my Compose project. It fails with some random project library jar, e.g.If I exclude this library from proguard, it'll fail with some next library - it can be both Compose one or any other, looks like message is unrelated to the problem.
By commenting code in the project, I've found out that I can fix the build by replacing one of
@StringRes param: Intin composable function withparam: String. But I still not sure if that's the root case.When trying to reproduce it in a sample project, I was able to reproduce it with even simpler code, that doesn't include int parameter. If I switch from compose-material to compose-material3, it builds fine.
MRE with dependencies is attached.