Thank you very much! I will investigate it. And yes we are using default debug sign way for debug builds. This remote sign is used just for release builds.
First few notes: - I'm expecting that your solution is valid for build plugin 3.3.X, right? It will not work on 3.2.X. - It is interesting that you suggesting to use variant.getFinalArtifact(). I'm currently using variant.outputs.each, because if I know every variant can have multiple outputs if apk split is enabled, or it is already removed in 3.3 (there is still no source code available if I know, but my current solution still works in this way.) - I'm signing also test apk by using variant.testVariant?.outputs?, it is still possible? - I still need to setup dependency on this APKAccessTask to handle that it will be run in the right time when apk or/and app bundle is prepared already. Currently, I'm using signTask.dependsOn output.packageApplication output.assemble.dependsOn signTask As you can se here <https://gist.github.com/tprochazka/09bc1fdf6da0de7ad0830c911d10028d>. And probably still need to call variant.outputsAreSigned = true. -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
