Sign auto generated apk by deploy-to-bitrise step using the same keystore to sign aab

Feature Requests Steps
1

Description of the feature request

Following up on this issue No way to opt out of universal APK generation · Issue #93 · bitrise-steplib/steps-deploy-to-bitrise-io · GitHub, when deploying a bundle (aab), the step automatically builds a universal APK out of it. However, it’s not signed with the same key, which is not useful for us.

Use case / for what or how I would use it

We will have to uninstall and re-install the app, when we want to test the apk from local build and the one generated from bitrise, as it was signed using different keystore. It is troublesome since we cannot install the apk directly without uninstalling the previous app first.

Solution:

  1. Sign auto generated apk by deploy-to-bitrise step using the same keystore to sign aab
  2. Let us generate the apk by ourself, sign the apk using the same keystore and deploy it to bitrise artifact, however you need to provide the opt out of universal apk generated by deploy-to-bitrise step as it is not useful and will only make confusion for user because of 2 universal apk
2

Hey there @daniel11, thanks for the feature request! :slight_smile:

3

is this issue planning to be addressed? I see that in bitrise documentation, universal apk will be signed with the uploaded signing key, but it is still being signed with the debug key.

4

Hi @dkim_discovery,

That’s correct, we have an item on our board to address this situation. There’s more information in this thread about the issue: https://github.com/bitrise-steplib/steps-deploy-to-bitrise-io/issues/93