App name not set correctly in Windows EXE metadata

Hi,

EDITED: This case is only about the item below. The case started out with more issues, but those are split off into separate cases and either already fixed, or related to issues outside Electron-packager. Only the item below remains:

• If I run the executable and right-click on its icon after it launched, the name ‘Electron’ still shows (but with the icon I specified)

INITIAL CASE DESCRIPTION: For the past day and a half I’ve been trying to package my app as a Windows executable. While the basic process works, I run into the following issues:

• If I look at the file details of the created .exe: – the ‘File version’ is still set to the used Electron version, although i specify another version – the ‘Product version’ is empty
• If I run the executable and right-click on its icon after it launched, the name ‘Electron’ still shows (but with the icon I specified)
• If I pin the app, a new icon is created (when right-clicking that it also shows ‘Electron’, but also with the icon I specified)

Note that the generated .exe did get the supplied fileName, the suplied icon and that ‘File description’, ‘Product name’, ‘Copyright’ and ‘Original filename’ are set as specified

In my main.js I do call this: app.setAppUserModelId('com.squirrel.myCompany.myCompany');

I work on Windows 10 and am using the latest electron-packager version and use electron 0.34.0

This is the command I use:

electron-packager .\app\ myCompany --platform=win32 --arch=x64 --version="0.34.0" --overwrite --app-version="1.0" --icon="myCompany.ico" --app-bundle-id=myCompany --helper-bundle-id=myCompany --version-string.CompanyName="myCompany Inc." --version-string.ProductName=myCompany --version-string.FileDescription=myCompany --version-string.LegalCopyright="Copyright (C) 2015 myCompany Inc. All rights reserved." --version-string.ProductVersion=1.0 --version-string.FileVersion=1.0 --version-string.InternalName=myCompany --version-string.OriginalFilename=myCompany

I’ve seen many cases related to this, but all are marked as closed and should be included in the latest releases.

As I’ve looked everywhere for solutions and tried all that I could find and none worked, I’m posting this as a bug.

[nithinc989]

Thanks for the reply, I figured out now that it was not an issue with npm, I had to use double quotes escaped and not single quotes. That solved my problem. In case anyone is facing similar issue they can use it as shown below. "elpackage": "electron-packager ./ MYCompany --platform=win32 --arch=x64 --overwrite --icon=./MYCompany.ico --win32metadata.CompanyName=\"MYCompany Inc.\" --win32metadata.ProductName=myName --win32metadata.FileDescription=\"MY Company\" --appCopyright=\"Copyright © 2015 MYCompany Inc. All rights reserved.\""

@malept It would be great if you could add certificate adding option in the electron packager itself. Now for adding the certificate I need to create a bundled exe using electron-winstaller. I don’t know if that is possible with packager but its just something that would be good to have if it can be done. 😃 . If it is already there could you please point me in the right direction.

[malept]

@nithinc989 this is probably an issue with NPM and not Electron Packager, if it works correctly when you run the command directly.