NativeScript / NativeScript/nativescript-cli
Build android release apk without signing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
From @ZuSe on March 12, 2018 13:18
We are using Jenkins for building, signing and uploading our native android apps.
As the keyStore containing our signing key is saved within the jenkins credentials manager I would also like to use the same process for our NativeScript-App.
Unfortunately I am not able to build an unsigned release APK (as you can do for example in Android Studio) using the tns command.
tns build android --release requires the specification of the keystore (which might not be installed on the building machine)
I would therefore suggest to let it build an unsigned-release.apk file similar to Android Studio / gradle assembleXXXRelease command which can then be signed by whatever key signer is preferred.
In case the key-path parameter is specified it should use the existing process but not require it per se.
Best
Patrick
Copied from original issue: NativeScript/NativeScript#5526
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the tns build android --release entry point and its key-path handling. Compare the requested behavior with Android Studio/gradle assembleXXXRelease, then verify that a release APK can be produced without a keystore while the existing key-path flow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- build-system, cli, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100