NativeScript / NativeScript/nativescript-cli
Release build key path accepts only absolute paths on Windows (can be relative on MAC)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
On Windows, building in release for Android is accepting only absolute path for the keygen.
e.g.
Windows
tns run android --bundle --release --for-device --key-store-path D:\my-release-key.jks --key-store-password <pass>--key-store-alias <alias>--key-store-alias-password <alias-pass>
On Windows only absolute paths are accepted - in this case the key is sotre d in D:
MAC
tns run android --bundle --release --for-device --key-store-path ./my-release-key.jks --key-store-password <pass>--key-store-alias <alias>--key-store-alias-password <alias-pass>
On MAC the path cna be relative to the root project e.g in this case the key is store in <project-folder>/my-release-key.jks
Using next versions of CLI, modules, nativescript-angular and dev-WebPack plugins.(demo app here)
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
Reproduce the Windows release Android build using the documented --key-store-path command, then compare it with the relative-path command shown for macOS. Trace how the NativeScript CLI resolves --key-store-path during release builds; done means a project-relative keystore path is accepted on Windows as well as an absolute path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- cli, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100