electron-userland/electron-windows-store

:package: Turn Electron Apps into Windows AppX Packages

electron-windows-store's Issues

Minimum Windows Version to Run Appx & Certificate Questions.

I have 2 questions:

1. I understand that to build the Appx, I need Windows 10 AU. But will my users also need at least this version in order to run the application?
   • The reason I ask is the Electron documentation seems a bit ambiguous with the text:
   • "With Windows 8, the good old win32 exectuable got a new sibling: The Universial Windows Platform."
   • Does this mean Windows 8+ can also run the application?
2. When Window AU is released, will I have to use a "Microsoft Certificate" or can I use an Authenticode Certficate that I already have purchased? or are those the same thing?

Edit: 3. Where can I get a Microsoft Certificate?

Clean output directory

UWP packaged app leaves files locked after closing

Not sure if this is somehow an upstream Electron issue that only manifests itself in UWP packaged apps.

Basically I'm packaging my application like so

  const child = spawn(
    path.resolve(__dirname, 'node_modules', '.bin', 'electron-windows-store.cmd'),
    [
      '--input-directory',
      '"dist\\Google Play Music Desktop Player-win32-ia32"',
      '--output-directory',
      'dist\\uwp',
      '--flatten',
      'true',
      '--package-version',
      '1.0.0.0',
      '--package-name',
      'GPMDP',
      '--package-display-name',
      'Google Play Music Desktop Player',
      '--package-executable',
      'Google Play Music Desktop Player.exe'
    ]
  );

  // spit stdout to screen
  child.stdout.on('data', (data) => process.stdout.write(data));

  // Send stderr to the main console
  child.stderr.on('data', (data) => process.stderr.write(data));

  child.on('close', (code) => {
    done();
  });

So pretty standard I think. When I run the application it launches correctly 🎉 And everything appears to work.

However when I close the application and attempt to run the normal non-UWP win32 version I get a load of "resource locked" errors on the shared files that I create while running the app (Settings and generic Data Storage).

Is this a limitation of the appx magic that is happening because I had to reboot my PC to get those files unlocked which is an absolute nightmare when developing 😢

Issue with Code Signing with CN that has Spaces / Special Characters

I was able to generate almost the complete package (the whole .appx was created) but my package keeps failing on the final code signing step with "Error: SignerSign() failed. (-2147024885/0x8007000b). Looking this up online says that this means that the publisher does not match the certificate CN; however, having checked it a million times I am sure that they are the same. I can sign other arbitrary .exe files so my cert is definitely valid.

My CN does, however, have spaces and a trailing period (Quorum Analytics Inc.). Is there any chance that that's the issue / that something isn't getting escaped correctly?

Identity Setup - Type Error - Windows Kit folder

electron-windows-store quits with an TypeError during first use.

You need to install a development certificate ... (Y/n)
Y
Welcome to the Electron-Windows-Store tool!
...
Please enter the location of your Windows Kit's bin folder: (C:\Program Files (x86)\Windows\Kits\10\bin\x64)
hit enter =>

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    ...
    at inquirer.prompt.then (...lib\setup.js:161:31)

Also happens when actually entering the path. I'm on a 32 bit machine - also tried C:\Program Files (x86)\Windows\Kits\10\bin\x86.

// edit
When I look at setup.js:161 this might be an issue w/ the input for the publisher identity. I entered two words (don't know yet what exactly goes in there).

node v6.2.1
npm 3.10.2

// edit 2:

setup.js:160 is the issue:

let publisher = dotfile.get().publisher.split('=')[1]

There's nothing to split as dotfile.get() returns an object and publisher already contains the actual content. That leads me to the thought that my input might be invalid.
What exatly goes into the identity prompt?

Guess those lines could use some extra explanation + some more robustness.

Question: Is the resulting App compatible with Assigned Access?

I'd like to run an electron application packaged as AppX with Assigned Access.

Is it possible?

developer certificate

@felixrieseberg Hello, please tell us about the developer certificate to obtain and how to generate devcert.pfx

restrictedcapabilities namespace is not allowed

During submission, I got this error
Package acceptance validation error: You don't have permissions to specify the following namespaces in the appx manifest file of the package ludosquest.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities

I imagine this allows to run full trusted EntryPoint="Windows.FullTrustApplication".

Any workaround here?

Everything in the output directory gets deleted!

The build script provides no warning that everything in the output directory will be deleted!
I was expecting a separate folder to be created inside the output path where all files needed for conversion would take place.

Trying to add icon with no success

im using --icon=src/assets/icons/win/icon.ico with no success For some reason the icon is just not changing.
Am I doing something wrong?

option to allow define icons folder

currently there is no way to define custom icons for the XML file generation. It would be great to somehow allow users to define a folder containing all icons

How to communicate between UWP background task and Electron processes

Is their currently a way, or is their a planned way to communicate events and information between Electron and the UWP background task.

I can't see a way to do this currently and the example didn't shine much light on the matter.

Really interested in using this to get access to the SystemMediaTransportControlsDisplayUpdater class but that requires sending current song information from Electron to the UWP background task.

How to make appx a "Silent" installer

I am currently in contact with windows desktop bridge consultant trying to get my app in the store. I am using electron-forge that is using electron-windows-store for appx and the consultant is telling me that the install needs to be silent and he is running into problems with his review tool because it's not
Any one have any idea what he means or how I could make it "silent"

Manifest Restricted Capabilites Error

When trying to upload my appx to the app store I am running into this error. The link no longer exists, so I don't exactly know how to fix it

Package acceptance validation error: You don't have permissions to specify the following namespaces in the appx manifest file of the package App.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities

Maximum call stack size exceeded

Hi!
I'm trying to convert my project to uwp app from electron and I'm getting this:
RangeError: Maximum call stack size exceeded at rimrafSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:256:15) at C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\remove\rimraf .js:298:5 at Array.forEach (native) at rmkidsSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:297:26) at rmdirSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\re move\rimraf.js:289:7) at rimrafSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:254:7) at C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\remove\rimraf .js:298:5 at Array.forEach (native) at rmkidsSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:297:26) at rmdirSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\re move\rimraf.js:289:7) RangeError: Maximum call stack size exceeded at rimrafSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:256:15) at C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\remove\rimraf .js:298:5 at Array.forEach (native) at rmkidsSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:297:26) at rmdirSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\re move\rimraf.js:289:7) at rimrafSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:254:7) at C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\remove\rimraf .js:298:5 at Array.forEach (native) at rmkidsSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\r emove\rimraf.js:297:26) at rmdirSync (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\node_modules\fs-extra\lib\re move\rimraf.js:289:7)

Don't really know if it's my error somewhere, electron app works just fine.
Also, if I choose to create new certificate I got

TypeError: Path must be a string. Received undefined at assertPath (path.js:7:11) at Object.join (path.js:466:7) at inquirer.prompt.then (C:\Users\Devamors\AppData\Roaming\npm\node_modules\electron-windows-store\lib\setup.js:173: 31) after entering a path to Windows Kit's bin folder

DPI settings not honored, window is blurry from scaling, not crisp like desktop electron or Chrome.

I'm creating this issue primarily as a tracking issue because I use Slack and I opened it up to find it was very blurry on Windows 10. It's unusably bad on a Surface Pro 3 at 150% scaling. Or at least, to my preferences, I'll uninstall and stick with the web app. Below you can see the Slack UWP app and the same text in Edge.

This is an aside for @felixrieseberg, but what are the technical merits of embedding Electron versus using a web application packaged for UWP?

Support for Manifest uap:SplashScreen

Would it be possible to incorporate support for the uap:SplashScreen element in the manifest XML file?
https://msdn.microsoft.com/en-us/library/windows/apps/dn934810.aspx

Unused stdout & stderr array vars

https://github.com/CatalystCode/electron-windows-store/blob/master/lib/zip.js#L9

Update README

Provide debugging methods

Essentially a simple "console.log from the main process now writes to file/windows logs".

Question regarding electron-builder / electron-packager

Hi there,

I've recently upgraded my electron app to be built by electron-builder. autoUpdate is working w/ Squirrel.

Now I see this package and my first thought is: "Awesome! Just what I was looking for". But on a second read I see that I need to have the outputs from electron-packager. Will Windows Store apps have an auto-update built in automagically (via Windows Store)?
Do I have to drop electron-builder / Squirrel when I want to use electron-windows-store and move (back) to electron-packager?

Fails executing *.ps1 script - restricted

Please enter your app's package name (name of your exe):
Please enter your app's package version:
Flattening modules...
& : Die Datei "...\ps1\flattennpmmodules.ps1" kann nicht geladen werden, da die Ausführung von Skripts auf diesem System deaktiviert ist. Weitere Informationen finden Sie unter "about_Execution_Policies" (http://go.microsoft.com/fwlink/?LinkID=135170).
In Zeile:1 Zeichen:6

• & {& '...
• CategoryInfo : Sicherheitsfehler: (:) [], PSSEcurityException
• FullyQualifiedErrorId : UnauthorizedAccess
  ...
  events.js:160
  throw er; // Unhandled 'error' event

Error: spawn ...\makeappx.exe ENOENT
...

Runnin Get-ExecutionPolicy in the PowerShell returns Restricted. Gonna change that and see what happens but this should probably go into the README / wiki. (This seems to be the default setting)

Add support for dynamic scaling of application images

We are still unable to get "dynamic scaling" working on app icons (defined within the AppManifest.xml within uap:VisualElements). I believe this is somehow related to the appx build process but I could also be doing something wrong.

As I understand it we would declare something like this:
Square150x150Logo="assets\Square150x150Logo.png"

And then provide the following image sizes:

assets\Square150x150Logo.scale-100.png (150x150)
assets\Square150x150Logo.scale-125.png (188x188)
assets\Square150x150Logo.scale-150.png (255x255)
assets\Square150x150Logo.scale-200.png (300x300)
assets\Square150x150Logo.scale-400.png (600x600)

The app or installer would then select the appropriate images based on the device form factor and pixel density. However we are unable to build the Appx installer when we do not also include a file without the scaling factors. I have read lots of blogs on this subject and I am still not clear what we might be doing wrong?

Take in a cert then sign the appx file with the cert

Provide programmatic access to methods

Support hardware/software not clear

I was looking at the documentation:
https://github.com/electron/electron/blob/master/docs/tutorial/windows-store-guide.md

It's not clear to me what it is supported. When uploading an electron-windows-store .appx users will be able to use my app on:

• Windows 10 (PC)
• Windows 8 (PC) ?
• Windows Tablet ?

From the doc: it will not runs on:

• Xbox
• HoloLens
• Phones ?!

Why not on Phones? If I need to support this I will need to use something like cordova?
Thanks

SyntaxError: Unexpected token =>

I'm having problems making this work:

C:>electron-windows-store --input-directory C:...\app.electrify.dist\my-electrified-app-win32-x64 --output-directory C:\aaaa\myelectronapp --flatten true --package-version 1.0.0.0 --package-name myelectronapp
C:\Users\gatsu\AppData\Roaming\npm\node_modules\electron-windows-store\bin\windowsstore.js:28
-flatten <true|false>', 'Flatten Node modules without warning', (i) => (i ===
^^
SyntaxError: Unexpected token =>
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3

issues with the generated xml file

Although the generated appx file works as expected I got the following errors during app submission

Package acceptance validation error: We don’t allow the capability you’ve specified: runFullTrust.
Package acceptance validation error: The PublisherDisplayName element in the app manifest of TDM.appx is Reserved, which doesn't match your publisher display name: *****.
Package acceptance validation error: You don't have permissions to specify the following namespaces in the appx manifest file of the package TDM.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities

If I remove the runFullTrust capability as well as the namespace, electron app would not run anymore (even the hello world example). I am not sure how to debug this appx.

flattennpmmodules.ps1, bad path for flatten

flattennpmmodules.ps1 is looking for ./node_modules/electron-windows-store/node_modules/flatten/bin/flatten but for me, there is no flatten under this path. Instead npm put it in the top-level node_modules.

Guess this is an artifact from times when npm didn't flatten the modules itself? flattennpmmodules.ps1 should probably check both paths:

1. ./node_modules/electron-windows-store/node_modules/flatten/bin/flatten
2. ./node_modules/flatten/bin/flatten

I'd file a PR but I'm not familiar with PowerShell :|

If parameter missing, ask for one

Allow Configuration params via CLI

Document AppService

Package acceptance validation error

Hey @felixrieseberg

I tried to submit my converted Electron application to the windows store and after jumping through too many hoops to count 😆 I ran into this glorious message on the Windows Store submission page.

Package acceptance validation error: You don't have permissions to specify the following namespaces in the appx manifest file of the package GPMDP.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities

And that URL that is provided 404's.... Do you have any idea what's going on here?

events.js:141: Unhandled 'error' event

Hi @felixrieseberg ,

I get the following error while generating the appx, any idea?

Thanks in advance!

flatten node_modules complete
Starting Conversion...
Cleaning output folder...
Copying data...
Creating manifest..
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn C:\Program Files (x86)\Windows Kits\10\bin\x64\makeappx.exe ENOENT
    at exports._errnoException (util.js:870:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)

Shipping 3rd party installers

Hey there,

currently I'm shipping a 3rd party installer with my application. It's run during setup. Do you see any way to include that installer when packing for the windows store?

My best idea right now is to somehow ship the installer (msi/exe) and explicitly run it on first app launch.

Handle Protocol Activation for appx

We need to make sure protocol activation works inside Electron. Let's also document how to set it and how to discover it.

Zip packaged app

Help using electron-windows-store

I am trying to use electron-windows-store to create AppX from my electron project. The code exited with this log file:

...
Running Installer in Isolated Environment


[2016-05-16T19:31:06] No installer valid exit codes specified. Using defaults: 0
[2016-05-16T19:31:06] Replace any occurence of <log_folder> in -InstallerArguments with C:\installer\logs
[2016-05-16T19:31:06] Running installer command in isolated environment:
[2016-05-16T19:31:06] Command Line = "C:\installer\ElectronInstaller.exe" 
[2016-05-16T19:33:11] Moving any logs in C:\DesktopAppConverter\bf927a11-9137-4a7a-8bfe-dff0c69c97a8\shared\logs to C:\Users\Am\Desktop\ss\logs
[2016-05-16T19:33:11] An error occurred. Refer to logs in C:\Users\Am\Desktop\ss\logs
[2016-05-16T19:33:11] Cannot create a file when that file already exists.

[2016-05-16T19:33:11] at Invoke-Sequencer, C:\Users\Am\Desktop\DesktopAppConverter\converter_util\Sequencer.ps1: line 165
at <ScriptBlock>, C:\Users\Am\Desktop\DesktopAppConverter\DesktopAppConverter.ps1: line 367

Any idea what could have gone wrong?

Unknown error, events.js:160

Ran electron-windows-store inside my build folder. Stepped through the questions:

• appconverter: n
• certificate: n
• publisher id: ...
• windows kit location: ...
• path to built app: ./path/to/my/packaged/app
• output path: default
• flattening: y
• package name: the name of the exe
• version: 0.9.13.0

It then starts flattening etc., starting conversion, cleaning output folder, copying data, and after printing Creating manifest.. this is what happens:

events.js:160
    throw er; // Unhandled 'error' event
    ^

Error: spawn ...x86\makeappx.exe ENOENT
    ...

Can't tell what went wrong. Any way to debug this?

Win 10 Pro @32bit, Version 1511 (Build 10586.589)
node v6.2.1
Windows SDK 10.1.10586.212
electron-windows-store: latest

Inject Environment Variable

We need a simple way for people to check if they're running in the Windows Store. We could either inject a file into the VFS (and then check for its existence) - or, alternatively, write a little C++ snippet that checks for a property only available within WinRT apps. The latter would be native and is maybe less desirable.

The application steals focus to Windows Touch Keyboard which cannot be used

I'm trying to run the attached project on Windows 10 Pro (latest version available without Windows Insider Program).

Basically it is a fullscreen browser window that navigate to http://www.google.com.
I configured Windows in Tablet mode, in order to let the touch keyboard popup whenever any text field in the page (in this case the query one) gets focused.
Then, I packaged the application with electron-windows-store in order to let electron work as Windows Store application.

When I start the application and Google home page is loaded I'm not able to use the touch keyboard, because it pops up but immediately disappears, like if electron tries to acquire again focus and causes touch keyboard disposal.

I tried also to disable fullscreen mode and setup frame coordinates in order to be as it was in fullscreen, but no success.

Any suggestion?

TestApp.zip

Fails on every run after creating a certificate

The first time I run electron-windows-store, I'm prompted to create a certificate, I create the certificate, and the app is successfully packaged and signed, but if I run it a second time with --publisher "CN=mycertificatename", it fails with this error:

SignTool Error: The specified PFX password is not correct.

Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe exited with code: 1
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-store\lib\utils.js:70:23)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe exited with code: 1
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-store\lib\utils.js:70:23)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

I also tried --publisher "mycertificatename" which produces this error:

Packing 3509 file(s) in "C:\sign-ftph\output\pre-appx" (content directory) to
Using "C:\sign-ftph\output\pre-appx\appxmanifest.xml" as the manifest for the
MakeAppx : error: Error info: error C00CE169: App manifest validation error:
RIALNUMBER|Description|PostalCode|POBox|Phone|X21Address|dnQualifier|(OID\.(0
fier|(OID\.(0|[1-9][0-9]*)(\.(0|[1-9][0-9]*))+))=(([^,+="<>#;])+|".*")))*'.
The attribute 'Publisher' with value 'criticalthinkingco' failed to parse.

MakeAppx : error: Package creation failed.
MakeAppx : error: 0x80080204 - The specified package format is not valid: The

Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\makeappx.exe exited wit
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-stor
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\makeappx.exe exited wit
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-stor
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

And without --publisher at all, I receive this error:

SignTool Error: The specified PFX password is not correct.

Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe exited with
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-store\
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
Error: C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe exited with
    at ChildProcess.child.on (C:\sign-ftph\node_modules\electron-windows-store\
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

And if I just delete .electron-windows-store, say no to creating a new certificate, and enter my certificate's name when prompted, I receive this error:

SignTool Error: File not found: undefined

So far the only way I've found to re-run electron-windows-store successfully is to delete the .electron-windows-store file and my certificate file and recreate the certificate when prompted.

Am I doing something wrong here? I'm having a lot of trouble understanding this tool.

Handle long path

Handle apps that have long file path. "Move-Item : The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."

Is Free Trial on Windows Store supported?

I'm in the process of submitting my paid electron app: http://friendlyfox.es/pawsfortrello/

I was wondering if you could offer any insight into limitations or possibilities of the Trial option on Windows Store? Is there something that would prevent it from working related to electron?

Assets scale not being recognized

I am trying to add my custom assets folder to add icons to my appx installer. For some reason it is not recognizing that these are the icons I want to use and is defaulting to the samples.
My folder does copy to the correct place and all of my icons are

Logo.scale-44.png
Logo.scale-50.png
Logo.scale-150.png
Logo.scale-310.png

And my config is:

        "assets": "./build/appxAssets/"

But, the appx still defaults to the samples instead

Splash screen support

Is it possible to support adding a splash screen asset?

Not sure if it'd just require the asset and manifest changes or if other changes to Electron would be needed, but it'd be nice to have!

Crash during setup - makecert.exe

Please enter the location of your Windows Kit's bin folder:
C:\Program Files (x86)\Windows Kits\10\bin\x86
Creating Certificate
When asked to enter a password, please select "None".
events.js:160
throw er; // Unhandled 'error' event

Error: spawn C:\Program Files (x86)\Windows Kits\10\bin\x86 ENOENT
at exports._errnoException (util.js:1007:11)
...

Win 10 Pro @32bit, Version 1511 (Build 10586.589)
node v6.2.1
Windows SDK 10.1.10586.212

Will appx be accepted into Windows Store?

Will my appx be accepted into the Windows Store?
I've ran the Windows App Certification Kit, it failed with several errors:
Platform version launch
App launch
App prelaunch
Restricted namespace
Binary analyzer
Supported APIs

The minimum version and namespaces have been created automatically.
Binary analyzer and Supported APIs are failing on files that were created by electron-windows-store.
Am I missing some settings?
Or does the WACK just need to be updated to allow electron based apps?

lib/flatten should just use Node

It's even using Node anyway, so we should just get rid of that PowerShell script.

cc @ritazh

Signtool fails when using p12 certificate.

We have a certificate with an extension of p12, when I try to use this I get the following error:
SignTool Error: The specified PFX password is not correct.
I've tried adding to the command line: signtool-params "/fd SHA256","/p password"
I've also imported the certificate to the certificate store on my PC.

I am able to sign the file as a separate step using: signtool sign /f path\Cert.p12 /fd SHA256 /p password appname.appx