-
-
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
dev-app-update.yml not found #1505
Comments
If you want to use updater in a dev mode, you need to add this file manually. |
Please specify electron version. |
electron version 1.6.6 Is there a template of what this file should contain? Not even sure where to find the generated app-update.yml.. |
@develar I'm not sure where to manually add this file either...
|
@zeevl I believe the generated file is |
@sebn Is this where you mean? As this doesn't seem to work. I could add it manually to |
@alexcroox Maybe you're confusing development and production setup? |
Yer I'm still confused unfortunately. I'm running The error I'm getting is I'm still not sure where to manually copy
Still the same error |
|
The work around for development for me is now
|
https://github.com/sindresorhus/electron-is-dev recommended. |
@develar Mate... The issue is you have a hard-wired check for dev-app-update.yml, already using the electron-is-dev module. It is using electron app.getAppPath() when dev mode is detected, which is generally going to point to default_app.asar when running 'electron' for dev. This makes no sense as it can't be implemented as we can't place a file there. So why have the code? You are awesome for making electron-builder/electron-updater, but I find a lot of your dev decisions very baffling and frustrating when encountered, unlike any other popular open source package I've used. Perhaps you should consider asking a couple of people to join a committee who bring a different perspective? Happy to help, I have 20+ years of SD experience, a lot of architecture. |
This referenced issue is breaking even production builds because I have 'electron' in my dev path which causes electron-is-dev to return true when it shouldn't. |
You should not use electron updater in the dev mode. |
That makes it incredibly hard to develop an updating system/UI if you have to build every time you change a line of code relating to the update system UX in order to test the result... |
I can understand it not being supported in dev mode, the update system must rely on an install having files in certain places. |
@alexcroox Please note — not "must", but "should". Want to test — no problem. Just create |
@TimNZ On macOS your update will be successful only if app is signed, but place doesn't matter (so you can run it not only from /Applicaitons, but from dist folder also). So, no way to test update fully, but you can test "update system UX" using |
To make clear — we are not going to improve this aspect without properly formulated issue request. (Hint: JetBrains IDEs allows you to debug packed applications, even in the asar, in the same way as you debug your dev build). |
@alexcroox If your issue is that dev file is not located correctly (The error I'm getting is Error: ENOENT, dev-app-update.yml not found in /Users/alex/Projects/xxxx/node_modules/electron/dist/Electron.app/Contents/Resources/default_app.asar.), I will check it now. |
@develar yer I added it to those 2 locations above but was still getting the error not found. Ran out of places to find that I might be able to place it |
Maybe this will help someone for solving this issue. For me it worked creating the My directory structure then looks like this
And in
And then normally start your main entry file with |
Hi, is the path issue fixed? for me
|
quick question, what is the format of the |
@ysfjwd
At least this is what is working for me |
@alexanderwe Hi
|
@zhanyouwei |
I get this on windows
Update:
solved my issue. |
When I run this locally with the fix above, it compares the latest release of my app to the version of electron rather than the app itself. |
Anyone manage to get this working with Amazon S3? I've burned half a day on this seemingly simple task. I get I can't even understand where the I understand it's recommended to test this in a packaged app, but that's not really feasible in every situation. I've tried setting the updateConfigPath and a every other tip I've found online and in this thread, and always All I'm trying to do with this right now is to get info about the latest update to show in the GUI =( |
Hope this saves somebody a day. In This little oversight cost me big time. I expected it would still check for updates, but it doesn't seem to from what I can tell. I assume this is because this isn't really a supported feature, there's no provided partial functionality for that function in development, seems to be the case. The promise always resolves with |
Creating a file dev-app-update.yml in root directory with following content fixed the problem for me of my generic server setup:
|
@nihalmpatel it worked like a charm!! thanks!! |
在根目录中创建具有以下内容的文件dev-app-update.yml可以解决我的通用服务器设置问题: |
Refs: - Testing auto updates electron-userland/electron-builder#3053 - electron-userland/electron-builder#1505 - electron-userland/electron-builder#1393
This is in relation to the recently-fixed #1254
Now, running
autoUpdater
usingelectron path/to/app
results inIs there something I should be doing to generate this file?
The text was updated successfully, but these errors were encountered: