Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong naming conventions #47

Open
chandrucrypto opened this issue Jul 8, 2021 · 1 comment
Open

Wrong naming conventions #47

chandrucrypto opened this issue Jul 8, 2021 · 1 comment

Comments

@chandrucrypto
Copy link

chandrucrypto commented Jul 8, 2021

This action does the great job, but I didn't understand the fact that why it generates app-release-unsigned-signed.apk. Can't it not be app-realease.apk to make the process simple? Also why do we need to do ./gradlew assembleRelease every time before calling r0adkll/sign-android-release@v1 as this can be called inside the action library itself..

@joakimcarlgren
Copy link

joakimcarlgren commented Sep 28, 2021

Hi @r0adkll
This is not a big deal, however a bit annoying that the signing step simply appends "-signed" onto the artifact, when there's an "-unsigned" already part of the name.

The ideal solution would be to check if there is "-unsigned" part of the name, and then replace that with "-signed", or provide the ability to set a name of the final signed apk/aab

ref:

const signedApkFile = apkFile.replace('.apk', '-signed.apk');

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants