-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
maker-dmg fails when run in parallel #3517
Comments
I have the same issue when building to arm and x64 using |
Also in with
|
Yeah me too. Is there any solution about that? |
same here, any suggestion? |
I use the code in this PR via this npm package:
|
This is my workaround: I just use a different name for the dmg maker on different archs: new MakerDMG((arch) => ({
name: `<app_name> Installer (${arch})`,
})), |
Pre-flight checklist
Electron Forge version
7.3.0
Electron version
N/A
Operating system
macOS 14.3
Last known working Electron Forge version
It broke in 7.0.0
Expected behavior
Expect
electron-forge make -- --arch=x64,arm64
to build both x64 and arm64 versions of the app.Actual behavior
Both x64 and arm64 make steps fail.
with the error
Target already exists
node_modules/appdmg/lib/appdmg.js:81:53
Steps to reproduce
electron-forge make -- --arch=x64,arm64
Additional information
For context it'll be helpful to read through this PR that changed how makers are run. #3363
I dug into this a bit.
the specific target error comes from
appdmg.js:81:53
On a run through with just one target that succeeded:
console.log("Target step started", global.target);
at the start of that shows
[REDACTED]/desktop/out/make/OurAppName.dmg
for both of the builds that are happening simultaneouslyI took a look at the electron code that calls into that
@electron-forge/maker-dmg/src/MakerDMG.ts
output on line 21 is the one used as the target.
forgeDefaultOutPath is fine though. For example:
[REDACTED]/desktop/out/make/OurAppName-1.2.3-arm64.dmg
dmgConfig is
Execution goes into the conditional (
if !this.config.name
)I think this could probably be fixed by adding the targetArch to the outPath.
I plan on submitting a PR to fix this soon.
The text was updated successfully, but these errors were encountered: