Skip to content

Checksum mismatch on Windows NSIS #1045

@Daymannovaes

Description

@Daymannovaes
  • Version: 10.8.1
  • Target: NSIS
    (building from windows too)

  • Node version: 6.9.1

  • npm version: 4.0.3

I'm getting checksum mismatch, like following in the screenshot

screenshot 18

I uploaded the executables with --publish=always at github and didn't change anything.
The fact that I'm checking for updates a lot of times even ater the download starts, can affect this?

Because just for test purpose, I put the check interval to 30 seconds, so I get update-available a bunch of times.

Plus, I'm getting everytime a different checksum. What's going on?

My autoupdater module is very simple:

autoUpdater.addListener('update-available', () => {
  logger.info('update-available');
});
autoUpdater.addListener('update-downloaded', (event, releaseNotes, releaseName, releaseDate, updateURL) => {
  autoUpdater.quitAndInstall();
});
autoUpdater.addListener('error', (error) => {
  logger.error('error when trying to check for update');
  logger.error(error);
});
autoUpdater.addListener('checking-for-update', () => {
  logger.info('checking-for-update');
});
autoUpdater.addListener('update-not-available', () => {
  logger.info('update-not-available');
});

async function setup() {
  autoUpdater.checkForUpdates();

  await sleep(30 * 1000);
  setup();
}
setup();

And but package config is simple too:

"build": {
    "appId": "some-id",
    "files": [
      "node_modules/**/*",
      ".env",
      "app/**/*"
    ],
    "publish": [
      {
        "provider": "github",
        "repo": "some-repo"
      }
    ],
    "win": {
      "certificateFile": "./certs/my_signing_key.pfx",
      "certificatePassword": ""
    }
  }

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions