Still getting the same thing. I've retried a few times -- some have gone through in 10 minutes, while others stay waiting. This has been happning more frequently in the last few weeks. createdDate: 2025-04-18T20:15:04.680Z id: c0de4060-e3b5-4bc5-ab78-1506c6863491 name: xxxxxxxxxxxxxxxxxxxxxxxxdmg status: In Progress -------------------------------------------------- createdDate: 2025-04-18T19:48:35.085Z id: 5e9a35ab-650d-47a0-b2cc-67719c9aac62 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-21T15:01:28.370Z id: 1638e3be-f5fc-444f-bdad-c81cc0c53992 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-21T23:12:42.074Z id: 1936ba0f-5fb1-4668-8a7b-ed5e033ddf79 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-21T18:52:03.112Z id: c96e60a5-beed-4ef3-8629-37486c31fb32 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-22T02:30:08.564Z id: 4bdc6a67-b4e5-4a29-8f35-701026f413e9 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-22T15:10:27.377Z id: 94fad92a-0f25-4a2c-ad37-382f5dedd83f name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress -------------------------------------------------- createdDate: 2025-04-22T18:39:47.671Z id: bbd84685-ac02-4f3a-976e-92e368e8be17 name: xxxxxxxxxxxxxxxxxxxxxxxx.dmg status: In Progress --------------------------------------------------

Last request that worked well: createdDate: 2025-04-22T17:57:17.900Z id: b37d6c51-4aca-4ae5-9441-03f61ce31f27 name: xxxxxxxxxxxxxxxxxxxxxx.dmg status: Accepted 1a) The only difference between this one and id b37...f27 is the version string in the package.json and package-lock.json. And this one failed because it couldn't mount the dmg. createdDate: 2025-04-22T18:39:47.671Z id: bbd84685-ac02-4f3a-976e-92e368e8be17 name: xxxxxxxxx.dmg status: Invalid First one that took a long time. Infact, it's still in progress after a week createdDate: 2025-04-15T12:40:23.734Z id: 057bc62e-4cef-4585-ac53-03c035b7615e name: xxxxxxxxxxxxxxxx.dmg status: In Progress First one that worked well after updating to the latest Electron createdDate: 2025-04-15T13:59:13.840Z id: 9d53d0bc-84b2-48a1-b385-7e1572cb8077 name: xxxxxxxxxxxxxxxxxx.dmg status: Accepted Thanks in advance for the help!

Our build process that uses electron-builder builds a .zip and a .dmg. The .zip contains the .app. The sign and notarize happens after the build is complete. I took the zip that contains the .app, and I signed and notarized that. The apple UUID for the notary is 9fea337f-94dd-49bb-9f75-6aeebc904cf3. I then unzip the zip to get access to the app, and I run the staple command xcrun stapler staple xxxx.app The output I get is Processing: /path/to/output/xxxx.app Processing: /path/to/output/xxxx.app The staple and validate action worked! Then, I create a disk image from the .app by hdiutil create -srcFolder "/path/to/output/xxxx.app" -o /path/to/output/xxxx.dmg //output ............................................................................................... created: /path/to/output/xxxx.dmg This seems to work. We're running into a different outcome than expected though. When I double click on a dmg, usually, the end user gets a splash screen prompting the user to drag the app to the applications folder. Do you have any instructions to create this splash screen?

[quote='837173022, DTS Engineer, /thread/781883?answerId=837173022#837173022'] Coming back to your main issue, my reading of our bug about this is that you’re submitting a disk image in UDF format. Is that correct? If so, why is that? It’s… well… unusual, to say the least [/quote] Yes, that is correct. It's a legacy bit of code that we had in place a couple years ago for backwards compatibility. Do you have a format that would be better recommended?