Documentation for updates.json ?

[manast]

Hello,

I am a quite confused about how I should build my updates.json file, it is a dictionary with keys mapping to some values, but how should be the keys constructed so that proper key is mapped to proper version?

[manast]

Could be something like: {target}-{arch}-{channel} ?

[megahertz]

yes, you're right. https://github.com/megahertz/electron-simple-updater/blob/master/example/updates.json

[manast]

@megahertz is there any property we can use to read out from the updater which key is using for checking for updates? i.e. some key that includes the {target}-{arch}-{channel} string. That would be quite useful for debugging since I cannot be 100% sure which key is using and since it is not updating I am just blind testing different namings.

[megahertz]

You can get the value using the updater.buildId property

[VynnykV]

You can get the value using the updater.buildId property

Hi, why I'm getting Update for win32-x64-prod-v1.0.1 is not available
What does it mean?

[megahertz]

@VynnykV If you have already published an update that means somethings isn't configured properly and you app can't find the update. Feel free to post your updates.json and updater settings here, I'll check what's wrong.

[VynnykV]

@VynnykV If you have already published an update that means somethings isn't configured properly and you app can't find the update. Feel free to post your updates.json and updater settings here, I'll check what's wrong.

I've tried to run your example, it displays nothing. I'm using it without electron-simple-publisher. What can be wrong?

[megahertz]

@VynnykV The example didn't work with the latest Electron. I just updated it for Electron 20.