Status Update
Comments
ap...@google.com <ap...@google.com> #2
ap...@google.com <ap...@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.
ap...@google.com <ap...@google.com> #4
sg...@google.com <sg...@google.com>
ap...@google.com <ap...@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?
ap...@google.com <ap...@google.com> #6
no we don't have a plan to backport this. why is this blocking you from upgrading ?
an...@google.com <an...@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:
an...@google.com <an...@google.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
Backporting of
android.os.Build.VERSION_CODES_FULL.BAKLAVA
used a value of 1.000.000.000 as that was the value present inandroid.jar
in the Baklava SDK revision 3. In revision 5 the value was changed to 3.600.000.The backporting should be updated to reflect the value which will most likely be the final value for the release.