Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's a lot of terminological/conceptual confusion in the current API. An .appx file should have an
AppXManifest.xml
which looks like the following, omitting unimportant elements:Notice that there are two separate identities: the Package Name, and the Application Id.
When you run
electron-windows-store
, it generates anAppXManifest.xml
from the config you supply. The template is here and it looks like:Notice in the variable names: it calls the package name
identityName
, and calls the application idpackageName
. These template variables are subtituted by the user-supplied config like so:This means, to create a correct
AppXManifest.xml
, you need to call it like so:This is very confusing, and has led to many tickets:
The best way forward would be to introduce a separate
program.applicationId
config, which is used in preference to thepackageName
.Additionally, this PR deprecates the
identityName
, because the best name is justpackageName
, as this is the established terminology.