electron-updater | Deprecated. Part of electron-builder now. | Runtime Evironment library
kandi X-RAY | electron-updater Summary
kandi X-RAY | electron-updater Summary
Deprecated. Part of electron-builder now.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Starts the app .
- Extract the tar .
- Read package . json data from a package . json file .
- Check if app is installed .
- Check the next hash content from the cache .
- Helper function to retrieve a sub - dependency version
- handle the update
- Execute the update .
- Get the binaries for a package .
- Ensures the application to an update .
electron-updater Key Features
electron-updater Examples and Code Snippets
Community Discussions
Trending Discussions on electron-updater
QUESTION
I would like to be able to open a deep link and take that protocol url and login with it. I have successfully got the electron app to open from the deep link but I can't seem to get the url or parameter from the deep link. I followed the tutorial from https://www.electronjs.org/docs/latest/tutorial/launch-app-from-url-in-another-app but I wasn't able to get it to work on ubuntu. In the tutorial it when you open from deep link it opens a dialog box but the open-url listener isn't getting called. Is there something I am missing to getting the open-url to work on linux.
Heres my index.ts
...ANSWER
Answered 2022-Mar-29 at 06:38Figured out what was wrong. The documentation has the linux and mac as the same but linux is different or at least on debian it is. The documentation says to put into the app.on('open-url', (event, url) event but this doesn't work for linux or at least it didn't work for me.
Apparently or what I found that you have to grab it from the arguments from when it is called by the operating system to open. So what I did was in the app when ready event is finished i did:
QUESTION
I have a repository that utilizes electron-updater for auto update. The weird thing is, it has no any code whatsoever pointing where the release updates are stored (I store it in GitHub releases), but somehow the autoUpdater.checkForUpdatesAndNotify() still works. There is github remote origin but I doubt it's being used by electron-updater to find the repository. I don't use any GitHub token either.
The way I release update:
- Increase the
versioninpackage.json - Run
electron-builder, producing.AppImage - Create new release draft in my repository's GitHub releases
- Upload the
.AppImagefile to the draft's assets and modify the draft's tag - Download the previous release, and then open it
- Voila! The update works. But how?
It's worth mentioning that if latest-linux.yml is missing from the latest release's asset, it will throw 404 error and refuse to update despite knowing the latest version's tag.
Here's the repository I'm talking about: https://github.com/SnekNOTSnake/fresh-update/releases
Also, is this how normal people release their electron app? I tried the electron-builder --publish way, but it's troublesome compared to the manual steps above.
ANSWER
Answered 2022-Mar-23 at 08:19Thanks to Caramiriel in the comment section above for the enlightenment.
How electron-updater knows where to find the repository is from resources/app-update.yml inside the produced .AppImage file.
The app-update.yml file is produced by electron-builder using the information from git remote get-url origin (if available).
I proved it by changing the origin's url to https://github.com/SnekNOTSnake/tofu-tracker.git and build the AppImage, and (surprisingly enough) the repo's value became tofu-tracker.
QUESTION
When I pack my Ionic project with @capacitor-community/electron packager (using electron-builder), I get the following error:
ANSWER
Answered 2021-Oct-03 at 18:22So, apparently problem lies in default publish method. You need to change your electron-builder.config.json file to the following form (without the comment):
QUESTION
When I update an Electron app using the electron-builder autoUpdater, all the file storage I defined is overwritten. What settings do I need to make these files persist?
Here is an MCVE example (for the main process):
...ANSWER
Answered 2021-Aug-21 at 14:55I managed to do this after looking at Cameron Nokes' excellent blog:
cameronnokes.com/blog/how-to-store-user-data-in-electron:
Storing user data in the operating system’s designated location for user’s app data is the idiomatic way for native app’s to persist user data because:
when we auto-update the app, our source files may get moved or delete
changing or adding to an app’s internal files will invalidate the code signature
To do this I used const userDataPath = app.getPath('userData'); to get a path to the OS' app storage location. and then changed the references to 'persistentFile' to String(userDataPath)+'/persistentFile':
QUESTION
I am trying to publish an electron app to my GitHub repository's releases.
Here is my package.json
ANSWER
Answered 2021-Jul-28 at 21:12Electron-builder will release your app on GitHub as a draft first, then you'll need to manually go in and publish the release.
Take a look in: https://github.com/sriramsridharanvr/sample-electron-app/releases
See if you can see any drafts that have been created.
QUESTION
ANSWER
Answered 2021-Jun-19 at 04:34First, try this solution. Edit your TypeScript Config file (tsconfig.json) and add a new key-value pair as
QUESTION
I Know that there is a lot of topic about this, but since none of them work, I must make a new one, I'm quite confused as why my electron app doesn't launch when I used yarn dev for my project, but when my friends try it, in his laptop, he can run and the apps launch normally without any problem, so Is there anyone here ever face the same problem with me? if there is someone, how can you solve this problem?
this is what my terminal looks like:
for information I used:
...ANSWER
Answered 2021-Apr-28 at 12:55This may be a silly answer. Try checking whether the task is running or any other programs interfereing the app, like an antivirus.
QUESTION
ANSWER
Answered 2021-Apr-15 at 17:21electron-builder does not include devDependencies in the packaged application since they're exclusive for development, you should reinstall electron-updater as a dependency.
From the electron-builder website:
A complete solution to package and build a ready for distribution Electron app for macOS, Windows and Linux with “auto update” support out of the box.
- NPM packages management:
- Native application dependencies compilation (including Yarn support).
- Development dependencies are never included. You don’t need to ignore them explicitly.
...
QUESTION
I'm building a project based off the Electron React Boilerplate project. I am running MacOS 10.15.7 and node v14.15.1.
I'm trying to install sqlite3 package. Since it's a native dependency, I ran yarn add sqlite3 inside the src/ directory, like it says to do here. The compilation fails with the following output:
ANSWER
Answered 2021-Mar-10 at 22:12I downgraded the sqlite3 package to v5.0.0 and it rebuilt correctly. Hope this helps anyone else with the same issue.
Source: nodejs electronjs sqlite3 - use of undeclared identifier 'napi_is_detached_arraybuffer'
QUESTION
I'm trying to implement autoupdate of my electron-react application using electron-updater and AWS S3 bucket. But getting error:
...ANSWER
Answered 2021-Feb-04 at 13:03As per the official documentation, you need to have something like this S3Options
AWS credentials are required, please see getting your credentials. Define
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEYenvironment variables. Or in the~/.aws/credentials.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install electron-updater
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
