Skip to content
This repository was archived by the owner on Nov 17, 2022. It is now read-only.

Update publishing-android-apps.md #496

Merged
merged 1 commit into from
Nov 25, 2016
Merged

Update publishing-android-apps.md #496

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion publishing/publishing-android-apps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,8 @@ You can publish a NativeScript app in *Google Play* the same way [you would rele
Both *Package Name*, and *Application Id*, are unique identifiers, provided by you for your app.
- *Package Name* is used to identify resources such as the `R`.
- *Application Id* is used to identify your app on devices and at the *Google Play*.
In the NativeScript framework, both are set to the `nativescript.id` in `package.json`.

In the NativeScript framework, both are set to the `applicationId` in `app.gradle`.
The NativeScript CLI build system will set them as the `package` attribute in the generated project in `platforms/android/src/main/AndroidManifest.xml`.
In the `app/App_Resources/Android/AndroidManifest.xml` it will use a placeholder: `package="__PACKAGE__"`. Do **not** modify the `package` attribute there.

Expand Down