problem with local email database

[TeoMorabito]

I tried updating to 1.10 and get stuck in a loop with the following error message Tried uninstalling and deleting the folder shown in the error message and it keeps coming back.

[evaristorivi]

Same bug. I return to 1-9-2

[michalzembron]

This issue was first reported 9 hours ago. And it is apparently happening to all Windows users who accept to update the application. Lay users won't know how to handle this strange message loop. So I think you guys should have suspended the offering of this update already until a fix is released.

Even better, on their official bug report forum, there are several submissions from 8 days ago about this update on Windows. 8 days without any dev noticing it? wow

And I don't mean I'm angry that they haven't released the patch to version 1.10 that fixes the issue yet because that's not always possible, but they just could stop offering the update to Windows users.

[Niko-Kk]

I wonder how many people have paid for mailspring to have this kind of a response, or fatal flaw not uncovered. Things like this, along with very little refining that I've seen over the years, leads me to potentially stop my subscription.

On Wed, Mar 9, 2022, 6:39 PM Michał Zembroń @.***> wrote:

This issue was first reported 9 hours ago. And it is apparently happening to all Windows users who accept to update the application. Lay users won't know how to handle this strange message loop. So I think you guys should have suspended the offering of this update already until a fix is released.

Even better, on their official bug report forum, there are several submissions from 8 days ago about this update on Windows. 8 days without any dev noticing it? wow

— Reply to this email directly, view it on GitHub https://github.com/Foundry376/Mailspring/issues/2373#issuecomment-1063186424, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5WJFY6P4XVXOQG3QWBE53U7DO6DANCNFSM5QIN37NQ . You are receiving this because you commented.Message ID: @.***>

[patricklamond]

I wonder how many people have paid for mailspring to have this kind of a response, or fatal flaw not uncovered. Things like this, along with very little refining that I've seen over the years, leads me to potentially stop my subscription. … On Wed, Mar 9, 2022, 6:39 PM Michał Zembroń @.> wrote: This issue was first reported 9 hours ago. And it is apparently happening to all Windows users who accept to update the application. Lay users won't know how to handle this strange message loop. So I think you guys should have suspended the offering of this update already until a fix is released. Even better, on their official bug report forum, there are several submissions from 8 days ago about this update on Windows. 8 days without any dev noticing it? wow — Reply to this email directly, view it on GitHub <#2373 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5WJFY6P4XVXOQG3QWBE53U7DO6DANCNFSM5QIN37NQ . You are receiving this because you commented.Message ID: @.>

I'm one of 'em.. pretty surprised it's the first update in a while and little to no support when it seems to be f'ed for all Windows users. I'll probably cancel Pro and go back to using PostBox (only app that works + doesn't look like garbage)

[vdisp]

For me, Windows must have did an update, since my computer was restarted in the AM, and Mailspring must have updated automatically. So, yes having the same issue.

Downloaded the old version: https://github.com/Foundry376/Mailspring/releases/tag/1.9.2

Reinstalled and seems to have fixed the issue for now.

[carterxx]

I am also having this same issue. Unable to bypass error loop - had to entirely uninstall application. Deleted folders mentioned in error, and checked for registry issues. Only way to get app functioning again was to reinstall using a previous install .exe, as most current install .exe from website results in same issue.

[Marvin-YYC]

I reinstalled ver. 1.9.2 but when I restart my PC Mailspring updates automatically. I have to delete the updated app again and reinstall 1.9.2 so this is only a temp fix. Hopefully they correct the issues with the update soon!

[madebylydia]

Hello everyone, I'm quite late into the party here, but I've personally made a little guide on how to rollback Mailspring to 1.9.2 the correct way! Hopefully this will help everyone here https://community.getmailspring.com/t/database-error-and-unable-to-launch-app-after-installing-v1-10-0/4063/11?u=predeactor I hope this will clear everyone's bad time into this little mess 😄

[theamazingaustin]

Following the suggestions above to delete the 1.10.0 folder (and reinstall 1.9.2 in my instance) resolved the issue for me. I'll just ignore the update prompt for now.

[Marvin-YYC]

Very Frustrating . . . . Too bad there isn't a way to turn off the automatic update in the preferences/settings. Every time the app restarts after v 1.9.2 has been installed it updates to the new v 1.10.0 and I have to start over again.

[Andychud]

Windows 11 here and exactly the same issue. Until this is fixed, I just disabled Mailspring from my starting automatically and changed my taskbar shortcut to previous version C:\Users\XXXX\AppData\Local\Mailspring\app-1.9.2\mailspring.exe

[foundry376-bot]

This issue has been mentioned on Mailspring Community. There might be relevant details there:

https://community.getmailspring.com/t/database-error-and-unable-to-launch-app-after-installing-v1-10-0/4063/29

[ali2077]

I also got this error message with weird Chinese characters and thought I was hit with a malware attack. what's happening to this app, really?

[omiazad]

I have the same issue. Installed older version and working fine.

[anwar3606]

I can bypass this error by placing the win32 build of better_sqlite3 inside \app-1.10.0\resources\app.asar.unpacked\node_modules\better-sqlite3\build\Release

But this raises another error saying NODE_MODULE_VERSION missmatch.
It expects version 97 but I can't find better_sqlite3 build for 97. In their release page they only have build for version 98, Does anyone have any idea how to build it for v97 ?

[KHulena]

I have the same issue and like others I re-installed the prior version which works but as soon as I close it auto updates and I am back in the loop. Is there any way to prevent this auto update? Or create a restore point so it's easy to go back to a prior version?

[Jean-luc57]

In C:\Users\"your_user_name"\AppData\Local\Mailspring\ I renamed Update.exe to Update.exe.old This prevents updating when closing

[githrdw]

I can bypass this error by placing the win32 build of better_sqlite3 inside \app-1.10.0\resources\app.asar.unpacked\node_modules\better-sqlite3\build\Release

But this raises another error saying NODE_MODULE_VERSION missmatch. It expects version 97 but I can't find better_sqlite3 build for 97. In their release page they only have build for version 98, Does anyone have any idea how to build it for v97 ?

@anwar3606 I got it working by cloning better-sqlite3 and running the following; npx --no-install prebuild -r electron -t 14.2.1 --include-regex 'better_sqlite3.node$' --arch ia32

Then Mailspring 'starts' with other module errors that seems to be Win32-phobic, fixing keytar will be the next step :/

[Marvin-YYC]

In C:\Users\"your_user_name"\AppData\Local\Mailspring\ I renamed Update.exe to Update.exe.old This prevents updating when closing

@Jean-luc57 Thanks for this, it solved the viscous cycle :)

[working-name]

I have long awaited the day where the decision to automatically update the application without a way to disable such terrible behavior would bite you in the ass. There you go, "smart" developer (whoever implemented that), you're missing an ass cheek now. Hope you learned from it.

[travisfont]

Also got this today when updating (coming from the default notification through Mailspring). After this failure, I decided to directly download a new installation executable from the official website, and ran as administrator, and STILL the same problem.

I could imagine that anyone who updates directly from the notification will face this corruption and fail to run the application from there.

As a programmer, this is a HUGE bug, and I am absolutely sure that Mailspring will lose a fair amount of users from this.

[working-name]

@tfont there's no way to stop the auto update from the UI, no off switch anywhere. You hit dismiss on the update, but the next time mailspring starts (reboot, logout, crash, user quit from sys tray) it'll be the updated version unless you find update.exe and rename it.

[travisfont]

@working-name unfortunately it's a pretty bad bug! from reading the comments it's an incompatibility issue with a newer version of SQLite. Seems like the Mailspring team didn't test on a Windows machine 😂😂

The good news is, if they update a hotfix quick enough to roll back the version, they won't lose as many users! The average windows user won't understand this loop and will simply uninstall and never use the app again.

[resiva]

*****[ Solved ]****

This is how you can survive this 1.10 update. btw noob here.

uninstall mailspring.

delete the items inside this folder C:\Users\XXXX\AppData\Local\Mailspring

{XXXX- Username}

download the Mailspring v.1.9.2 here : https://github.com/Foundry376/Mailspring/releases/download/1.9.2/MailspringSetup.exe

and install the same.

open and sign up and add just 1 account.

close the Mailspring app in the Task Manager to shut it completely.

go to C:\Users\XXXX\AppData\Local\Mailspring

Find the file "Update.exe"

rename the file into "Update.exe.old"

go to this folder

C:\Users\XXXX\AppData\Local\Mailspring\app-1.9.2

find and right click on the file "mailspring.exe" and Click " Send to - Desktop (create Shortcut)"

come to desktop and find the "mailspring - Shortcut".

Use only that shortcut file to open the Mailspring from hereafter.

If error occurs repeat from step one.

Hope this Helps!

[bliet]

Same here. And even if I kill the process via Task Manager, the message is shown again... in a loop. Bye bye mailspring.

[resiva]

Same here. And even if I kill the process via Task Manager, the message is shown again... in a loop. Bye bye mailspring.

Leave the loop in the background and continue the step from Renaming Update.exe.old file.

Hope this helps.

[KHulena]

I am no techy, but I opened the file location C>programData>xxxx>mailspring and in this file there was the sneaky update file which has the bug, along side old app 1.9.2 and I deleted this bug file and renamed the update.exe.old.

Fingers crossed I have shut down and restarted twice and it is still working

K

On Thu, 10 Mar 2022, 4:46 pm Benjamin Lietzau, @.***> wrote:

Same here. And even if I kill the process via Task Manager, the message is shown again... in a loop. Bye bye mailspring.

— Reply to this email directly, view it on GitHub https://github.com/Foundry376/Mailspring/issues/2373#issuecomment-1064274838, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYEUDJMQMZCFHNRRVV6CBLLU7IROPANCNFSM5QIN37NQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

[foundry376-bot]

This issue has been mentioned on Mailspring Community. There might be relevant details there:

https://community.getmailspring.com/t/database-error-and-unable-to-launch-app-after-installing-v1-10-0/4063/38

[Marvin-YYC]

Hope they release a fix soon! Hope it corrects this current problem along with several other bugs that make me crazy.

Does anyone know how to turn off conversation view?
I don't like conversation view and can't see a way to turn it off.

[shiipou]

Hope they release a fix soon! Hope it corrects this current problem along with several other bugs that make me crazy.

Does anyone know how to turn off conversation view? I don't like conversation view and can't see a way to turn it off.

Sorry @Marvin-1802 : https://community.getmailspring.com/t/disable-threading-conversation-view/290/2

[steffenu]

Already started testing some alternatives .... like emclient ... pretty major that I have to come to github to find a solution ....

[aliyazdi75]

We are on the third day and still, nothing happened. I don't quite understand why don't you use the revert button on GitHub and think about a solution later?

[patricioriba]

Hola me funcionaba perfectamente hasta que lo actualice y me sale este error lo he desistalado y he vuelto a instalar la version anterior y funciona todo en win10 atentamente Patrick

[githrdw]

I got it working by manually building some packages (the way I described here).

You can download and unpack my prebuilt packages in here: %LOCALAPPDATA%\Mailspring\app-1.10.0\resources\app.asar.unpacked\node_modules

(replace folders better-sqlite3, cld, keytar and windows-quiet-hours)

https://github.com/Foundry376/Mailspring/files/8231008/node_modules.zip

[rajwanur]

I got it working by manually building some packages (the way I described here).

You can download and unpack my prebuilt packages in here: %LOCALAPPDATA%\Mailspring\app-1.10.0\resources\app.asar.unpacked\node_modules

(replace folders better-sqlite3, cld, keytar and windows-quiet-hours)

https://github.com/Foundry376/Mailspring/files/8231008/node_modules.zip

Cheers, I can confirm that this method solve the issue. I was able to start Mailspring 1.10.0 without any issues, retaining previous data from 1.9.2. Thanks @githrdw

[DrBones]

Thank you @githrdw !

The prebuild node packages worked for me too, and now 1.10.0 (or a Frankenstein version of if) runs with the 1.9.2 data. Also it doesn't automatically update anymore or present the update hint.

Nice Workaround!

[kevinjaygonz]

I got it working by manually building some packages (the way I described here).

You can download and unpack my prebuilt packages in here: %LOCALAPPDATA%\Mailspring\app-1.10.0\resources\app.asar.unpacked\node_modules

(replace folders better-sqlite3, cld, keytar and windows-quiet-hours)

https://github.com/Foundry376/Mailspring/files/8231008/node_modules.zip

Confirm works !!!! Thanks

[Darthagnon]

I had the same bug (Win10 v1709); was very worried when I saw the chinese characters (where on earth are those from? CCP doing pull requests? )

Mailspring uses Squirrel autoupdate on Windows, for the unavoidable updating. Also used by Fork. As many of you have already found out, rename/delete the updater exe to disable autoupdate. imo a very bad design decision. Not to mention Squirrel is more-or-less unmaintained, which can be risky for online systems. Why implement malware-like autodownloads? Not a fan in Chrome/Edgium which started this trend. All updates should go through manual approval process by the user.

[working-name]

We are on the third day and still, nothing happened. I don't quite understand why don't you use the revert button on GitHub and think about a solution later?

Because that requires common sense.

[foundry376-bot]

This issue has been mentioned on Mailspring Community. There might be relevant details there:

https://community.getmailspring.com/t/error-with-the-local-database-during-update/4179/22

[Marvin-YYC]

Wow! I'm sure happy that this is a free service, there's no way I would pay $8/month for pro now with this sort of response.

Looking at Mailbird again, which I've used before and was happy with, but a little pricey.
There is Twobird, pretty good, but only for Gmail and Outlook. And there is Bluemail and EM Client too, but I think EM is overly complex for most personal user applications.

[working-name]

Wow! I'm sure happy that this is a free service, there's no way I would pay $8/month for pro now with this sort of response.

Looking at Mailbird again, which I've used before and was happy with, but a little pricey. There is Twobird, pretty good, but only for Gmail and Outlook. And there is Bluemail and EM Client too, but I think EM is overly complex for most personal user applications.

Postbox might potentially be a significant alternative - not open source, not free, and they forgot about linux users 😞

[madebylydia]

@githrdw May I mention your solution/fix into my post? Or do you think it would be a bad idea to do so?

[githrdw]

@Predeactor of course! Only thing is that this fix is somewhat temporary, so an upcoming update or re-install will remove these files.

[githrdw]

@Darthagnon My assumption is that the title in the message box is not rendered properly. Electron 14.2.1 is using Chromium it's base::UTF8ToUTF16 to convert the app title to a default title. In the Chromium docs however, there is this statement:

// These convert between UTF-8, -16, and -32 strings. They are potentially slow,
// so avoid unnecessary conversions. The low-level versions return a boolean
// indicating whether the conversion was 100% valid. In this case, it will still
// do the best it can and put the result in the output buffer. The versions that
// return strings ignore this error and just return the best conversion
// possible.

So I guess it is a bug in Electron resulting in this Chinese-looking string because UTF8 to UTF16 went wrong. I understand your reaction but I think this has nothing to do with China. Your second statement about Squirrel and auto-updating is something I agree with, it is bad behaviour to update automatically and use outdated updater-frameworks.

Some traces I followed: Mailspring error generator we all have seen in it's full glory https://github.com/Foundry376/Mailspring/blob/3be72eee5c10a43f6fb9924ab1e9a33bb0f5216e/app/src/browser/application.ts#L287

Electron 14.4 dialog src https://github.com/electron/electron/blob/8f487aa2cfe2a613a53b6b3552d7da3a374041da/atom/browser/ui/message_box_win.cc#L100

Chromium src https://chromium.googlesource.com/chromium/src/+/HEAD/base/strings/utf_string_conversions.h

[bengotow]

Hey folks! Thanks for the reports of this issue, we're looking in to it and will ship an update as soon as possible. I really apologize for it taking this long to get a fix out the door.

It sounds like everyone is on Windows, but are all of you also using Windows 32-bit? I've been looking into this for hours and I think that our CI service provider moved to 64-bit machines and it caused our native node modules to implicitly build for 64-bit as well.

👍 for 32-bit, 👎 for 64-bit

[spartanhooah]

Glad to finally get a response, but I'm switching to Blue Mail. It has a built-in calendar, which I like.

[githrdw]

@bengotow Looks like Mailspring is running as a 32-bit app. I am using Windows 11 21H2 (must be 64-bit because there is no 32-bit version of Win 11 ;)

[vdisp]

64bit Windows 10 here, however, MailSpring is running as a 32bit app as noted above.

[bengotow]

Hey folks, thanks for the updates - could you give this version of Mailspring a spin? I believe it will resolve the issue and we can ship a patch:

https://mailspring-builds.s3.amazonaws.com/client/5cf60d4b/win-ia32/MailspringSetup.exe

Thanks for your patience and help tracking this one down! I understand a mail app being broken for a few days is a major disruption to most of your workflows. If you pay for Mailspring Pro, please email me at ben@foundry376.com - I'd be happy to credit your account for a few months as a thank you for sticking with us through the Electron 14 upgrade!