You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the feed URL is constructed from process.arch which doesn't offer any insight into how the app that's calling it is built. I'm not sure it's possible for the running code to determine how the app has been built.
I think in theory we only need universal apps if the user doesn't know what they need to download, but when we are querying for updates, we know the user's architecture, like you suggest, there seems to be something like a preferred order to check:
<user's arch>
universal
finally falling back to x64 (since these can run on the m1s, and maybe what the user originally downloaded anyway).
Have you looked into the code at all to see if this is a straightforward enhancement you could put together a pull request for (both here and at update.electronjs.org)?
Currently the feed URL is constructed from
process.arch
which doesn't offer any insight into how the app that's calling it is built. I'm not sure it's possible for the running code to determine how the app has been built.My sense is that having a matrix of possibilities (darwin + x64, darwin + arm64, darwin + universal) to check would be worthwhile. Obviously this will also require some work in https://github.com/electron/update.electronjs.org to support it; I've filed electron/update.electronjs.org#140 to track that.
The text was updated successfully, but these errors were encountered: