question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Linux build is not using productName

See original GitHub issue
  • Version: 19.18.0

  • Target: linux squirrel

I am trying to build for Linux with -- linux configuration and I am using productName in package.json.

For a mac build, productName is picked up correctly for both artifacts (dmg and zip).

For linux name is being used. This causes an error.

I cannot use name for product name as my app is also a scoped npm package.

package.json example:

"scripts": {
  build:mac: build --mac,
  build:win: build --win,
  build:linux: build --linux,
},
"version":"0.0.0",
"name": "@myscope/my-package-name",
"productName": "My Desktop App",
"build": {
    "appId": ".....",
...

Error:

xorriso : FAILURE : Cannot acquire drive '.../repos/electron/myapp/build/@myscope/my-package-name-0.0.0-x86_64.AppImage'
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'

    at .../repos/electron/.../electron-builder-util/src/util.ts:67:16

I have a related issue for Windows Squirrel but that has a workaround (thanks to @develar for pointing it out):

https://github.com/electron-userland/electron-builder/issues/1879

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:8
  • Comments:18 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
probonopdcommented, May 30, 2019

Please reopen, this still seems not to be working: https://github.com/tunepack/tunepack-desktop/issues/6#issuecomment-497230517

When

"name": "tunepack-desktop", 
"productName": "Tunepack", 

is set, then we currently get

Tunepack-1.0.6-x86_64.AppImage would be expected. In other words, the dmg and the AppImage should always use the same name.

1reaction
achingbraincommented, Aug 18, 2017

The correct option to set is linux.artifactName.

e.g. package.json

{
  "name": "@my-scope/my-package"
  ...
  "build": {
    ...
    "linux": {
      "artifactName": "my-package-${version}"
    }
  }
}
Read more comments on GitHub >

github_iconTop Results From Across the Web

Common Configuration - electron-builder
If not specified inside of the build configuration, productName property defined at the top level of package.json is used. If not specified at...
Read more >
Electron app won't install if name is different than product name
However the problem comes when I change the productName field in my package. json file.
Read more >
System is not properly subscribed - Red Hat Customer Portal
Product Name : Red Hat Enterprise Linux Server Status: Not Subscribed Unable to find available subscriptions for all your installed products. So ...
Read more >
cinfo - IBM
Displays the product name, version, build information and application support propagation status (the “SDA STATUS” column) for installed agents. Use the cinfo - ......
Read more >
electron-packager
For creating distributables like installers and Linux packages, ... If appname is omitted, this will use the name specified by "productName" or "name"...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found