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.

`productName` isn't being respected on Linux

See original GitHub issue

Version: 7.21.0

Target: deb/AppImage

package.sjon

...
"build": {
  ...
  "linux": {
    "arch": [
      "ia32",
      "x64"
    ],
    "target": [
      "deb",
      "AppImage"
    ]
  }
  ...
}
...

app/package.json

...
"name": "hyper",
"productName": "Hyper",
...

Expected behavior

As per the docs, after running build, dist/linux-unpacked/Hyper should be present.

Actual behavior

After running build, dist/linux-unpacked/hyper is present – instead of Hyper.

I believe this regression was introduced here 😕

Issue Analytics

State:
Created 7 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

develarcommented, Nov 5, 2016

but my concern is the inconsistency between the 3 platforms – it was consistent before

AppImage since begging use name, but not productName for executable (because space in the executable causes (mostly fixed now, but anyway) weird issues).
You cannot modify macOs executable name after sign — weird things will happen. So, it is better to use name on macOs also. But we cannot change it due to backward compatibility (you must not change executable name once signed app is delivered to customers). So, productName for now on macOs.

So… I don’t think it is inconsistent. We build app according to platform/target conventions, not according to some unified and artificial standard.

1reaction

matheusscommented, Nov 4, 2016

To be clear: hyper is not suitable because the name of the app is Hyper 😅