-
-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building app fails when there are spaces in the APP_NAME field of the .env file #343
Comments
I'm facing the same isssue here. |
For now I’m just removing the spaces from the 2 package json files before building the app. It still takes the name from the .env file for the actual build (which can still have spaces in it), so it’s more of a pain than a real problem. |
Okay, I'm also doing the same before I was able to build. |
Are you using double quotes??? I have spaces in my app name value with double quotes and work fine, here is my example
|
I've managed to reproduce this. A fix is coming in NativePHP/electron#106 |
i have the same issue using ionic capacitor. removing the space does fixes it. |
What were you trying to do?
Trying to build my app on an Apple Silicon Mac, targeting Apple Silicon Macs
What happened?
When there are spaces in the APP_NAME field in the .env file, the build fails. Error message:
electron-builder version=24.13.3 os=23.0.0
Invalid name: "Example Name 2025" failedTask=build stackTrace=Error: Invalid name: "Example Name 2025"
How to reproduce the bug
Note:
Simon said on Discord:
3) is expected because we intentionally rewrite the app name in the package.json when we run native:serve as a way to show the correct app name in debug builds (which Electron doesn't support by default)
so the problem looks like electron-builder doesn't like the spaces in the name
i'll take a look at this later
Package Versions
PHP Version
8.3
Laravel Version
11.19.0
Node Version
22.5.1
Which operating systems have you seen this occur on?
macOS
OS version
14.0
Notes
No response
The text was updated successfully, but these errors were encountered: