I switched to signing my .apk with apksigner instead of jarsigner out of necessity, and the “Deploy to Bitrise.io” step’s public url is now showing the app-release-bitrise-aligned.apk (aligned) version of the apk to download which fails when trying to install. Is this a bug?
I know I can change the “Deploy directory or file path” field, which does work when I assign it to $BITRISE_APK_PATH. It seems like the public url has some logic somewhere to just grab the first .apk it sees in the deploy folder, which doesn’t seem ideal.
I verified in the logs of the signing step that BITRISE_SIGNED_APK_PATH and BITRISE_APK_PATH are pointing at the correct signed apk path.
