feat(cli): setup Android signing

[lucasfernog]

Tweaks the default Android project to include a simple setup for Android signing.

Example Github Action usage:

- name: setup Android signing
        working-directory: src-tauri/gen/android
        run: |
          echo "keyAlias=${{ secrets.ANDROID_KEY_ALIAS }}" > keystore.properties
          echo "password=${{ secrets.ANDROID_KEY_PASSWORD }}" >> keystore.properties
          base64 -d <<< "${{ secrets.ANDROID_KEY_BASE64 }}" > $RUNNER_TEMP/keystore.jks
          echo "storeFile=$RUNNER_TEMP/keystore.jks" >> keystore.properties

[amrbashir]

maybe we should just include keystore.properties by default instead of the dummy one, or even just remove this altogether and just document how users might want to add signing later on if they wish.

[lucasfernog]

i'd be fine with this on docs instead @FabianLars @simonhyll

[amrbashir]

It used to be in the docs but was lost in recent refactors of tauri documentation and whether we merge this PR or not, I think we will still need to have it documented

[lucasfernog]

@FabianLars what do you think about this standard approach vs a documentation based one? I'd like to get this resolved asap..
Personally I like giving an easier path to this for users for DX, but I also agree this is usually handled by docs instead.

[amrbashir]

I was going to PR the guide today, maybe I will do it tomorrow

[FabianLars]

I really like the idea (though we should also document the manual approach) but maybe it makes more sense to match the other platforms where we rely on env vars (or maybe both)?

[amrbashir]

I opened a PR for signing guide tauri-apps/tauri-docs#2337 anyways as it needs to be documented nonetheless

[lucasfernog]

I really like the idea (though we should also document the manual approach) but maybe it makes more sense to match the other platforms where we rely on env vars (or maybe both)?

in this case i think it's dangerous since we would end up writing secrets in plain text..

[lucasfernog]

I opened a PR for signing guide tauri-apps/tauri-docs#2337 anyways as it needs to be documented nonetheless

if we merge this PR we also need to update that guide btw

[lucasfernog]

another reason to merge this is that it helps people that do not commit the gen folder

[amrbashir]

another reason to merge this is that it helps people that do not commit the gen folder

didn't we change that behavior? at least it should be fine to not ignore gen folder by default, there is only a couple of files that should be ignored and we can add them in the .gitignore

[FabianLars]

Yes, we changed it, but that doesn't mean that everyone will want to commit the folder if they don't intend on changing files in it (ignoring the context of this pr)

[lucasfernog]

by default we gitignore the gen folder IIRC

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: npm/typescript@5.5.2

View full report↗︎

[amrbashir]

by default we gitignore the gen folder IIRC

we don't, we only ignore gen/schemas

[amrbashir]

the problem with this PR approach is it just as broken as if it wasn't configured, I would say even more broken, since without you can build your unsigned apk successfully but with this, it will always fail until signing is configured.