Status Update
Comments
je...@google.com <je...@google.com> #2
ga...@google.com <ga...@google.com>
je...@google.com <je...@google.com> #3
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.
je...@google.com <je...@google.com> #4
je...@google.com <je...@google.com> #5
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?
je...@google.com <je...@google.com> #6
no we don't have a plan to backport this. why is this blocking you from upgrading ?
sp...@google.com <sp...@google.com> #7
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:
72...@gmail.com <72...@gmail.com> #8
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.
Description
In b/258677934 I found that I could specify
r8.runInSeparateProcess
by adding this to settings.gradle :However, when I try to set jvmArgs in the same way, it doesn't have an effect:
This appears to be because
says
rather than