Location of app-update.yml

• Version: electron-builder 13.5.0 electron-updater 1.6.1

• Target: Win x64 MacOS

It looks like appUpdater checks for app-update.yml inside the electron dist/resources folder. Without it you’ll get an error like:

Error: Error: ENOENT: no such file or directory, open 
'C:\Users\mike\AppData\Roaming\npm\node_modules\electron\dist\resources\app-update.yml'

This is problematic because if you install electron globally and use it to run applications using electron path/to/app, you will need to change the file depending on which app you’re running. Even if electron is installed locally you have to place the file in there to do any testing.

I would suggest first looking in the app folder that is running, and then falling back to the electron folder if not found. Or make it configurable so we can set the location.

[mikecao]

@develar You’re right, code signing does cause a problem. I tested macOS and got the error, Could not get code signature for running application. I assume the same thing will happen when Windows signing is required.

I think my workaround is good enough for now since it allows me to at least test the update request. This probably doesn’t need a fix. But It might be helpful to update the wiki to tell people they need to manually copy the app-update.yml after building if they want to test in dev. Or load it themselves using updateConfigPath.

[mikecao]

Maybe something like this will work?

autoUpdater.setConfig({
  provider: 'generic',
  url: 'https://website.com/download',
  channel: 'latest'
});

Production can still use the app-update.yml file while in dev you will have to configure it manually.