NativeScript / NativeScript/nativescript-cli

Creation of multiple App Ids for Debug and release in package.json

Open
#4,410 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

configurations feature
Dominant language
JavaScript
Stars
1.1k
Forks
204
Avg merge
1d 9h
Merged PRs (30d)
8

Description

The article below explains the need to have two seperate android apps for debug and release purposes in order to keep the analytics data clean.

https://firebase.googleblog.com/2016/08/organizing-your-firebase-enabled-android-app-builds.html?m=1

defaultConfig { applicationId "com.company.project" // etc... } buildTypes { debug { applicationIdSuffix ".debug" } release { // etc... } }

From Nativescript 5.0.0+, the app ids mention have to be done in package.json as explained in the following link:
https://docs.nativescript.org/tooling/changing-appid

"nativescript": { "id": "org.nativescript.myappid" }

However the documentation only mentions regarding a single ID for the project.
Is there any way to work with multiple IDs for android itself (debug and release IDs)?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the package.json nativescript.id setting and the linked changing-appid documentation, then trace how the CLI applies that value to Android debug and release builds. Done means establishing whether separate IDs can be configured for those build types and documenting or supporting the resulting configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, javascript
Domain
cli, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.