Auto update in Electron app works, but is not relaunching application. #204
Comments
|
I've seen similar issue in our Electron app - When I call quitAndInstall, the app quits but does not relaunch. After some examination I found that the ShipIt process in Activity Monitor. If I kill that process, the update goes through. So I'm wondering if there's some kind of deadlock going on. I did a sample of stack trace of the ShipIt process when it happened again, and here's the stack trace: |
|
+1 |
|
Have similar problem, but after manual relaunch a see that app didn't updated actually (even version in application is the same). Where I can find any logs of this process? |
|
I've found a workaround, if you delete the ~/Library/Caches/appname.ShipIt/ folder before checking for updates and calling quitandinstall, there is no issue. I'm guessing there are some leftovers that seem to block the next update. I've applied this temporary workaround but would very much appreciate a fix :( Ok never mind i spoke too soon, the bug seems to be random and the workaround does nothing... :( |
|
Seeing this one as well @Andrew1431! Exactly the same sequence of messages in the ShipIt stderr log. |
|
I have hit this problem with VSCode update and following 52 lines are added to |
|
See microsoft/vscode#105114 as well |
|
Is anybody still seeing this? We're seeing it with a small subset of users on Electron 12.0.6. We use electron-updater, and when electron-updater's version of Logs reformatted for easier reading. Is there a workaround? I'm going to ask this user to But does anybody know what's going on here? 98% of our users get auto-updated correctly, but a small handful seem to get left on old version of our app due to something in electron-updater/Squirrel/ShitIt land. @Stanzilla I'm curious what you find related in that VS Code ticket? It seems separate to me? |
|
@aguynamedben Looks like that in your case (electron-userland/electron-builder#6120) electron-updater doesn't play any role, since update downloaded and transferred to Squirrel.Mac correctly. electron-updater only sends update to Squirrel.Mac but doesn't touch user file system. |
|
This could be an issue with electron autoUpdater, this is what I've found so far: After checking for updates, I get these events from autoUpdater:
// ~/Library/Caches/com.electron.appname.ShipIt/ShipItState.plist
{
"launchAfterInstallation": false,
// more stuff
}If I call But if instead, I check for updates again, I get these events:
And after that, if I try to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey there! I've got an electron app that is successfully checking for and installing updates. But after the successful update, the application is not starting. A manual restart of the app shows a properly updated application though.
Within
ShipIt_stderr.logfor my application, this is my error message.A quick google of "OSStatus -10814" brought me this error.
Let me know what additional information you would need for this.
The text was updated successfully, but these errors were encountered: