Cordova buildconfig.json keystore path

Clash Royale CLAN TAG#URR8PPP
Cordova buildconfig.json keystore path
How can I set Cordova buildconfig.json global path for keystore different than then the relative path where I've stored buildconfig.json.
Example:
I stored buildconfig.json in /home/user/test-app/build/sign
A part of buildconfig.json in which I've set a path to the custom keystore
...
"android": {
"debug": {
"keystore": "/home/user/keystores/test-release.keystore",
...
Gradle shows an error, bad location of keystore
/home/user/test-app/build/sign/home/user/keystores/test-release.keystore
1 Answer
1
In order to generate signed apk’s, we use a build.json config file that sits in the root of the project.
Our build.json file looks something like this:
"ios":
"debug":
"codeSignIdentity": "iPhone Distribution",
"provisioningProfile": "xxxxxxx-xxxxx-xxx-xxxx-xxxxx",
"developmentTeam": "xxxxxx",
"packageType": "ad-hoc",
"iCloudContainerEnvironment": "Development",
"buildFlag": [
"LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks""
]
,
"release":
"codeSignIdentity": "iPhone Distribution",
"provisioningProfile": "xxxxxxx-xxxxx-xxx-xxxx-xxxxx",
"developmentTeam": "xxxxxxx",
"packageType": "app-store",
"iCloudContainerEnvironment": "Production",
"buildFlag": [
"LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks""
]
,
"android":
"debug":
"keystore": "../build-config/android/xxxx.keystore",
"storePassword": "********",
"alias": "xxxxxx",
"password": "********",
"keystoreType": ""
,
"release":
"keystore": "../build-config/android/xxxxx.keystore",
"storePassword": "********",
"alias": "xxxxxx",
"password": "******",
"keystoreType": ""
,
"device":
"keystore": "../build-config/android/xxxxx.keystore",
"storePassword": "*******",
"alias": "xxxxxx",
"password": "*******",
"keystoreType": ""
,
"emulator":
"keystore": "../build-config/android/xxxx.keystore",
"storePassword": "*******",
"alias": "xxxxxx",
"password": "*******",
"keystoreType": ""
I found it here.
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.