Skip to content

[question] How can I test auto updater flow? #3053

Closed
@AoDev

Description

@AoDev

Version

  • "electron": "2.0.3"
  • "electron-builder": "20.15.3"

Target

  • OSX
  • Windows

This is a question I posted on Stackoverflow.
Not receiving answers I wanted to "proxy" it here, I hope it's fine, let me know.

The goal is to understand and extend the docs section auto-update debugging. I am copying the question here but feel free to answer it on Stackoverflow.

"Note that in order to develop/test UI/UX of updating without packaging the application you need to have a file named dev-app-update.yml in the root of your project, which matches your publish setting from electron-builder config (but in YAML format)"

So I actually have two questions:

  1. How do I actually test the auto-update flow?

Do I need to actually publish a new version to trigger an update locally? Seems pretty unclear, it would be like developing against the production server.

  1. Is it possible to have a fallback for unsigned code?

I don't have yet any certificate for code signing. So the OS/app will block the auto-update. But, I'd still want to tell the user that an update is available so they can go and download the app manually. Can I do that? (going back to point 1, I'd like to be able to test this flow)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions