Closed winie closed 2 years ago
as far as I'm aware it's not possible to build unsigned apk/aab even if you do not provide keys, some defaults are used to generate a signature.
If you don't want to pass your secrets to your CI, then just generate some random keystore, pass it to the CI and resign it locally with a real keystore.
Also, note that sdk46 will be the last supported version in classic builds, so I recommend migrating to eas (you can build for android without specifying credentials there) https://blog.expo.dev/turtle-goes-out-to-sea-d334db2a6b60 https://docs.expo.dev/build-reference/local-builds/
Feature Request
Build unsigned APKs/ABBs.
Motivation Behind Feature
Our app is built via Gitlab/Gitlab Runner. This forces us to store the certificate as a gitlabrunner variable, because turle-cli refuses to create APKs/AAB without a certificate. The Gitlab Runner and the Gitlab is used by several companies/institutes, which is why uploading the signing keys is bad from a security point of view. It would be better if the APKs and the ABBs are built unsigned by turtle-cli in the gitlab pipeline and we download the APKs/ABBs from gitlab and sign them ourselves on secure systems.
Unfortunately, turtle-cli refuses to build the apps if no signing certificate is provided:
Feature Description
Turtle-cli builds apps even if ''--keystore-path'' and ''--keystore-alias'' parameters are missing. An unsigned APK should be generated, which you can sign yourself.
Alternatives or Workarounds
Upload the signing key/certificate as a base64 encoded file to gitlab as a gitlabrunner variable.