Windows software update broken due to publisherName with no cert
See original GitHub issue- Version: 20.38.5
4.0.6
- Target: Windows / NSIS
A previous version of our app MyMonero (1.1.7) has a publisherName
set in package.json
. We didn’t realize auto-update wasn’t working in this version (a 404 was occurring - which is now fixed) … and now in the new version 1.1.8, once the update downloads, the app throws an error (which then causes the app to quit - very undesirable, I must say… since it breaks the app for everyone on Windows) … which says "New version 1.1.8 is not signed by the application owner: publisherNames: MyMonero Pty Ltd., rawInfo: { "SignerCertificate": null, "TimeStamperCertificate", null, "Status": 2, …
.
I’ve tried removing publisherName from the 1.1.8 package.json but it seems like it’s grabbing publisherName from the existing version 1.1.7’s config. I’ve also tried using verifyUpdateCodeSignature: false
in 1.1.8 package.json but again it seems to be using the 1.1.7 config (which would make sense).
This issue seems similar in principle to https://github.com/electron-userland/electron-builder/issues/1856 , however, we do not actually do any code signing on Windows yet.
Is there any way we can fix this issue for people on 1.1.7 so that the app doesn’t quit?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6
Top GitHub Comments
我今天也出现了这个问题,并且没有找到解决方案。这个问题对于用户当前的应用程序是致命的,现在看来,用户只能手动下载你的1.1.8,虽然这有点糟糕。
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.