parsify-dev / desktop

Next generation notepad-based calculator, built with extendibility and privacy in mind.
https://parsify.app
214 stars 2 forks source link

Error: Unhandled Promise Rejection - sha512 checksum mismatch #8

Closed LarsJandel closed 4 years ago

LarsJandel commented 4 years ago

This error just popped out of nowhere:

Unhandled Promise Rejection
Error: sha512 checksum mismatch, expected lpoYIgKOzWfd+yLGdtDaoiDjkFT6LuaDimXst5cAyjNOyfrlmWuOjb1xGCziygB2ISPArDdd30kcxlgT+YjQPA==, got eytX1BeQGaCqZSjpU7222lEnJ0N8kjFm1aiJvxq2cEgLrRoiaaivmKzUj+hMT/WC5pmiYRbLciUK1d5GRpeNVQ==
    at newError (C:/Users/UserName/AppData/Local/Programs/parsify-desktop/resources/app.asar/node_modules/builder-util-runtime/out/index.js:212:17)
    at DigestTransform.validate (C:/Users/UserName/AppData/Local/Programs/parsify-desktop/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:409:35)
    at DigestTransform._flush (C:/Users/UserName/AppData/Local/Programs/parsify-desktop/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:393:14)

LarsJandel commented 4 years ago

I think it is related to the auto-updater of Parsify, which isn't working for me: I can see sth. happening in the dedicated update folder, but just getting the error mentioned above. Running v1.0.1 and I know there is v1.0.2. Closing and starting the app didn't help, also using the button in the about page. I tried to manually install the latest version, but that resulted in another error: Unhandled Promise Rejection TypeError: Cannot read property 'value' of undefined at C:/Users/UserName/AppData/Local/Programs/parsify-desktop/resources/app.asar/app/background.js:1:4429 and Parsify launched with a white UI and using electron default behaviors within the menu, e.g. going to the electron website. Uninstalled and reinstalled v1.0.1, which works. But v1.0.2 works fine on another machine, where I did a fresh install (Parsify wasn't installed there previously). [Windows 10]

xxczaki commented 4 years ago

I'm currently in process of rethinking the way auto-updating should function. In terms of the value error - it is occuring because the existing configuration doesn't contain default values for features added in the next release. This can be fixed by deleting the config.json file located in %appdata%/Parsify Desktop (on Windows).

The next release (1.1.0) will include configuration migrations, so such errors won't happen anymore. I want to release it later today or tomorrow.

LarsJandel commented 4 years ago

Thanks for the workaround! Note, as I couldn't find the file right away, I found another Parsify folder within Roaming I didn't see before - containing that file, so I uninstalled Parsify, deleted that folder and was able to manually install v1.0.2 🎉 \AppData\Roaming\Parsify Desktop\ Thanks

xxczaki commented 4 years ago

1.1.0 is now out with configuration migrations. I also replaced the "silent" auto-update with a notification. This should also be useful with https://github.com/parsify-dev/desktop/issues/7, although as I said - I'm still not 100% sure about the current auto-update state.

xxczaki commented 4 years ago

This issue should be fixed in 1.1.2 with the new auto-update endpoint.

LarsJandel commented 4 years ago

Well, this error just popped again as well... [Parsify v1.2.0 | Windows 10]