NativeScript / NativeScript/nx
Trouble with application id and custom nativescript.config.ts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 68
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I have this project.json setup where the nativescript.config-aaa.ts contains a different appResourcesPath than the default (nativescript.config.ts). This seems to work fine.
However, I'm also building for different environments, and have to set the application id based on that, so I add "id" to the config.
"app-test": {
"flags": "--config=nativescript.config-aaa.ts",
"id": "com.app.aaa.test"
...
"app-dev": {
"flags": "--config=nativescript.config-aaa.ts",
"id": "com.app.aaa.dev"
The problem is that the id replacements happens in the default nativescript.config.ts, while the rest of the build process is using the specified nativescript.config-aaa.ts.
Any tips on how I can handle this situation properly?
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 with project.json and compare how --config=nativescript.config-aaa.ts is used with how the application id is replaced in nativescript.config.ts. Reproduce the app-test and app-dev builds, then verify that the selected custom configuration receives the corresponding id while retaining its appResourcesPath.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100