Closed jagthedrummer closed 2 months ago
I'm seeing what seems to be the exact same issue. When I package my app with electron-forge
(which calls electron-osx-sign
under the hood) in my local computer the signing works 100% of the time. But inside a GitHub workflow it's a toss. I'd say it hangs 80% of the time, but sometimes it just works.
Any suggestions would be appreciated.
Actually I think I was able to solve this by using this action (or potentially this fork with the update for Node 20).
Before I was essentially running this script which I'm not very sure where I copied from, but there are many places with similar instructions.
After migrating to the Github Action instead of the script everything works fine. My guess is that there's something in the codesign process that by default requires user interaction and that the action correctly disables while the script does not.
Glad this is fixed!
@VerteDinde I don't think this is fixed. I'm still having this problem from time to time.
I have an electron app that I build in GitHub Actions and every now and then, seemingly randomly, builds will stall and never complete the very first
codesign
operation.When things work correctly the first
codesign
call happens in a fraction of a second, and then it continues walking the tree and callingcodesign
for hundreds of other files.When the problem occurs the first
codesign
call stalls for up to 20 or 30 minutes (depending on the timeout set for the GitHub Action) and never finishes.Here are the last few lines from a stalled build:
And here's what a successful build looks like in that same bit of the log:
This seems similar to an issue reported a while back on the
electron/packager
project: https://github.com/electron/packager/issues/701But I already have the suggested solution as part of my keychain setup script.
And the problem I'm running into isn't persistent. Most of the time my builds work as expected. When the problem occurs usually it will fail a time or two (or more 😞) and then eventually work after some retries.
I've also set
DEBUG=electron-osx-sign
in my environment, but I'm not sure if I'm getting debug output fromelectron/osx-sign
. (Maybe some of what I posted above is the debug output?)