-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nsis app from fall 2017 (electron-updater 2.10.0) won't update to new version #2583
Comments
I want to add, that it can be proven that this is a compatibility problem with a old version of electron-updater / electron builder. Because updates work fine when trying to update an app from the current version of electron-updater (2.20.2) to the current version of electron-builder (20.0.4), as can be seen in below log:
|
Lastly, if this is a problem with |
I am sorry for late reply for donated issue. Please manually edit your version: 2.4.3
files:
- url: SMRT Web Setup 2.4.3.exe
sha512: EeH6GIq0KQDV8yZGGbYTB3cJSpoBaRy8iJUtYt92fBEakC8ORfhJxRBAtzTwbQ5WxpFTpq9SFdh0/dj0+HiSAA==
path: SMRT Web Setup 2.4.3.exe
sha512: EeH6GIq0KQDV8yZGGbYTB3cJSpoBaRy8iJUtYt92fBEakC8ORfhJxRBAtzTwbQ5WxpFTpq9SFdh0/dj0+HiSAA==
packages:
ia32:
size: 42154533
sha512: RKJFpUB73t3uUwl1FhAjV6NJpb527TizUDvixySjymGvsd+iuTVSgCTxRR9pwyl6MZD4LrQikjHPm8jr94vgFw==
blockMapSize: 43921
path: smrt-systems-2.4.3-ia32.nsis.7z
file: smrt-systems-2.4.3-ia32.nsis.7z
x64:
size: 48954140
sha512: 73NzPpv9SJxSg1HKNIaN7O1DN0xOGQ9L30W+goqFbGoVKV7gz49mDqqzITlVfVqVJCe2DaAnVUJEwQaeTLkbGQ==
blockMapSize: 52006
path: smrt-systems-2.4.3-x64.nsis.7z
file: smrt-systems-2.4.3-x64.nsis.7z
sha2: 8567a04b9f42f9958c3fe7f41bf0022175fc8d0af5887d43de562eb65773374e
releaseDate: '2018-02-14T17:49:15.454Z' Upcoming electron-builder will add |
Updating I see some computers having trouble updating though. However I don't think the issue is related, just my integration with If you look at my code I have What's happening is, I get a |
Never mind this is just a loop that it continuously finds that an update is available. Upon reboot of app update succeeds. However maybe it could still be considered a best practice to stop polling upon receiving the |
I think, better solution is to check updates only when app is started. It depends on your app, of course (e.g. tray app that started on launch, but... even in this case your target OS is Windows, so, machine restarted quite often). Only in very, very specific cases user needs to update app very often. No need to interrupt user work — checking on app launch is enough. And it leads to superior user experience — just download update (if available), notify user that update will be installed on quit, and nothing more. Recent version of electron-updater has function |
You are right @develar . I've updated my code to run |
Hey @develar , so as you suggested, we moved to Our software is a POS system, and at the end of the day users will sometimes just "shut down the computer" without first quitting our app. If there's an update to be installed, one of three things will happen:
Situation #3 is the only really bad one. It actually generates a lot of support tickets after releasing a new version, where we need to help users reinstall the app. Our users aren't very tech savy.. Sometimes users try to "fix it themselves" and use the MS backup recovery tool which takes them back to an even older version of our app. I've come up with some potential solutions:
The ideal solution for us, would be on that works on both Windows and OSX. I think that would be solution #1? Given your input, I'm happy to create a new issues better describing this problem. Also, if you see a major development that's needed, we're happy to donate... Also, thank you for a great project. |
As far I understand, you don't have such issue on macOS? Yes — the main issue as far I see it is fact that installing to directory is not atomic. Instead of writing new files directly to installation location, we can write new files to a temporary directory and then rename. But in any case it will be not really reliable solution.
thanks to @MariaDima solution "install update on launch if available" is easy now. |
@develar and @MariaDima , thank you! We haven't launched our app for OSX yet but we're about to in the next weeks. So just trying to find the best update solution for osx as well.. |
Squirrel.Mac is used under the hood. And I doubt that it will have such issue.
#2474 is merged now. How it is related — ability to reuse downloaded update not only right after exit, but any time later. |
@develar I see, thanks. |
Hi, I have a windows electron app that's in production with with electron-updater 2.10.0 / electron-builder 19.30.2.
Today I tried to deploy and update with electron-builder 20.0.4 and electron-updater 2.20.2. However the clients failed to install the update with a weird 404 when trying to download the .exe (see logs below)
I'm publishing a dual x64 x86 nsis-web installer to s3, this is the same as with the version that's in production currently.
Here's the latest.yml that the clients are fetching from: https://s3.amazonaws.com/smrt-releases/latest.yml
Here's the installer clients are downloading: https://s3.amazonaws.com/smrt-releases/SMRT+Web+Setup+2.4.3.exe
Also, here's my electron-updater implementation/class that outputs the logs you see. The code is the same in the old version of my app and the new one that I'm trying to update to.
Here's my build config in package.json. Likewise, this has not changed between current production build and my new build.
Here's my publish command (npm run publish):
Here's the final output of the publish command, uploading to S3 successfully:
The text was updated successfully, but these errors were encountered: