electron-builder: hdiutil exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE

On Ventura 13.0.1 managed to solve it by allowing application (in my case the terminal I was using to run the build) to update or delete other applications. It is in Privacy & Security -> App Management.

This worked for me, thanks.

On Ventura 13.0.1 managed to solve it by allowing application (in my case the terminal I was using to run the build) to update or delete other applications. It is in Privacy & Security -> App Management.

I would suggest the Full Disc Access, as well, for Terminal.

Since updating to Big Sur 11.3.1 I am receiving this same error message and I am unable to build a dmg file.

Xcode: Version 12.5 (12E262) Python: 2.7.16 electron: “~11.4.5” electron-builder: “^22.11.1”

just kill terminal and start fresh one i am sure it will work

Closing per comment above 🙂

I’m having this issue too, tried all suggestions mentioned above but none helped. The first time I tried building, everything went smoothly and I got all the output formats. Strange that it worked the first time but not anymore. I also tried wiping the node_modules and dist folders but no luck.

Unfortunately, I’m still seeing this issue. I’ve tried disabling spotlight and giving terminal permissions possible.

MacOS: 12.3/12.3.1 electron-builder: 22.14.13 Intel Mac

Hey all, yesterday I did some tests and running this command sudo mdutil -a -i off it works !!!

This may be a PROBLEM of BigSur system.

Adding the DEBUG_DMG=true env to the process could check out the ERROR.

In my case, the outputted ERROR was Operation not permitted when hdiutil create which is first step for creating dmg file.

SOLUTION: removing this line will always works well.

The -fs is one of HFS+, HFS+J (JHFS+), HFSX, JHFS+X, MS-DOS, or UDF. -fs causes a filesystem of the specified type to be written to the image. -fs can change the partition scheme and type appropriately. -fs will not make any size adjustments: if the image is the wrong size for the specified filesystem, create will fail. -fs is invalid and ignored when using -srcdevice.

ERR_ELECTRON_BUILDER_CANNOT_EXECUTE is a generic error. It would be helpful to see the actual error from hdiutil which should be written to console when running with export DEBUG_DMG=true. Do we understand the underlying issue down to running the hdiutil command in isolation and why it is failing?

We know that “hdiutil create”, when it fails, always fail due to failing to unmount (resource busy). Why that is is hard to say though. Could perhaps be antivirus or something else touching the files while the volume is mounted as has been suggested before. I can’t really tell if that’s the case. It seems to succeed eventually if retrying. For me that seldom requires more than three attempts.

I’ve tried running it in isolation quite a few times now with about the same result: it sometimes succeeds and sometimes fail. The success-error ratio seems to be much better though with failures happening less than half the time.

And the obvious thing that I should have tried from the beginning: running hdiutil with -debug

@EdmarPereira Looks like it might be related to what you had discovered before. The debug output reveals some unmounting problems:

detachTempimageFile: synchronous unmount /dev/disk3s1 returned 49168

and

2020-12-11 02:46:45.163 diskimages-helper[3922:2771162] detachTempImageFile: synchronous unmount /dev/disk3s1 [temp] returned 0x0000C010 (49168)
2020-12-11 02:46:45.165 diskimages-helper[3922:2771162] detachTempImageFile: synchronous eject /dev/disk3s1 [temp] returned 0x0000C010 (49168)
2020-12-11 02:46:45.165 diskimages-helper[3922:2771162] _detachTempImageFile: returning 49168

and finally

DIHLDiskImageCreate() returned 49168
hdiutil: create failed - Resource busy