Is anybody else getting this error messagebox? I’m getting it in an infinite loop when I try to start the app.
We encountered a problem with your local email database. We will now attempt to rebuild it.
Error:
\\?\C:\Users\Username\AppData\Local\Mailspring\app-1.10.0\resources\app....\better_sqlite3.node is not a valid Win32 application.
Was Mailspring cross compiled? In the past better-sqlite3 has had some cross compilation bugs (which are admittedly currently closed).
Of note, file tells me: \better_sqlite3.node: PE32+ executable (DLL) (GUI) x86-64, for MS Windows. So, not a Win32 application, but a Win32 (Win64) DLL.
Same problem. I had a support call from someone in a state of panic since they waited on the urgent acceptance of quotes and without that acceptance their installation teams cannot go out. Since there is no old version of Mailspring or old installer available on that machine the better alternative is to say bye-bye to Mailspring for good.
As a workaround for this annoying issue, you can terminate the process, then delete the 1.10. files and folders (should be in C:\Users…\AppData\Local\Mailspring). Take care, that the older version (for me it is “app-1.9.2” stays there. Then Mailspring will start the normal way and asks you, if you want to update, which you should decline.
Same here, Windows 11. Had to kill the process tree to end a failure loop, delete the 1.10 directory and install 1.9.1. Pretty disappointing. Did they test on Windows?
Same here, Windows 11, working fine for at least one month, suddenly get this failure loop, will not get out of it without CTRL+ALT+DEL. Only way was to install 1.9.1. Tried updating that install to 1.10 afterwards, got the failure loop back.
Looking forward to not having to deal with permafail loops.
It definitely appears to be a bad update that wasn’t tested properly. I was having the same issue this morning after the update to v1.10. I was able to follow guidance from @bowihowi4u and manually deleted the v1.10 files & folder (in C:\Users…\AppData\Local\Mailspring) and changed the Mailspring launcher icon to point back to the v1.9.2 folder.
Everything seems to be back to normal now - definitely going to ignore the prompt to install v1.10 update until I see confirmation this issue has been addressed.
This isn’t the first time this has happened…at least to me. This is happening again. I reinstalled the previous version and made sure to get rid of the 1.10 stuff. As soon as I close Mailspring and open it up again, I get this loop.
At this point, I am ready to ditch Mailspring. As much as I love it, I honestly cannot take time out of my day to fix this error every time it comes up.
