Closed ArmelChesnais closed 1 year ago
As a follow up, I've extended the display turning off to 3hr and disabled the mac going to sleep when display is off. I'm also keeping an eye to keeping the macbook process active during building/notarizing, and it seems to be helping with not crashing, though it's not 100%.
Of note, on my machine, interrupting the process from command line(ctrl-c) while notarize was awaiting completion would immediately and reliably cause the crash/restart. (the few times I tested it)
I have the same problem too.
I've been having this issue for months now too, it seems to work every now and then and sometimes just hang all the time. Also sometimes when it hangs, it causes a kernel panic and a purple screen restart.
Edit: I'm on a Mac Mini M1
This is affecting me as well; same symptoms as the others. I’ve only ever successfully notarized once, on my first attempt - all subsequent attempts cause very, very bad things to happen to the machine. On one instance, I saw the Wi-Fi connection fail entirely. On another, the keyboard stopped responding in other apps…?
I believe this issue is specific to the altool legacy notarization workflow. I was able to work around it and get notarization consistent by:
xcrun altool —list-providers -u “myapple@id.com” -p “appp-assw-ordh-ere”
Look for the WWDRTeamID.
This change needs to be made by 2023 by everyone anyway, and notarytool is faster, so there’s very little downside to this workaround.
Would still love to get to the bottom of why shelling out to altool has such dire consequences on the M1, but this at least gets things up and running again.
I believe this issue is specific to the altool legacy notarization workflow. I was able to work around it and get notarization consistent by:
- getting my team ID by manually running altool
xcrun altool —list-providers -u “myapple@id.com” -p “appp-assw-ordh-ere”
Look for the WWDRTeamID.
- edit your JS configuration for electron-notarize to add two new properties: { appBundleId: … … appleIDPassword: … teamId: “ID_FROM_PREVIOUS_STEP”, tool: “notarytool” }
This change needs to be made by 2023 by everyone anyway, and notarytool is faster, so there’s very little downside to this workaround.
Would still love to get to the bottom of why shelling out to altool has such dire consequences on the M1, but this at least gets things up and running again.
Thanks, I've tried this method only once and it worked first go, hopefully this fixes it. It's more like an upgrade than a workaround. I've done a bit of digging recently and found that it could be related to [different] methods used to upload to Apple's notarization servers. And your solution using notarytool to fix this makes me think that might have been the case.
Fixed by using notarytool instead. Closing per #141
I used to deploy/notarize my electron app on an intel macbook pro (intel 2015). It's run into the recalled battery issues for that model, so I've replaced it with a MacBook Pro (13-inch, M1, 2020) while I wait for it to be repaired.
Issue is however that electron-notarize appears to completely crash the M1 (full shutdown and restart) if it is interrupted.
The computer going to sleep interrupts it, causing the crash. Disabling sleep seems to indicate that notarize simply hangs forever sometimes, and never resolves (had it sitting for over an hour, which I'd never seen on the intel macbook). Trying to ctrl-C out of the process also interrupts notarize, causing the crash. Of note, notarize doesn't seem to hang every time, as I've had one build that did eventually resolve, but all previous and subsequent ones seem to get stuck indefinitely.
electron-notarize 1.2.1 node v14.16.1 electron-builder 23.0.2
notarize script as follows:
upon restart, all I see in terminal is the following from the restored terminal window:
Mac crash report as follows: