Closed TeoMorabito closed 2 years ago
I have the same problem. I tried uninstall and reinstall. Problem persists.
Have deleted. Hope you are able to correct this soon.
same, what a coincidence I found this literally just now from google
I was getting this too, on win11, I was able to launch the old version from this folder for now
The same for me.
Same here, quite curious of what happened for all of us to have the same issue at the same time right now... I reverted to an older version with no issue (fortunately I still had an old installer on my computer)
Same here, quite curious of what happened for all of us to have the same issue at the same time right now... I reverted to an older version with no issue (fortunately I still had an old installer on my computer)
i'm guessing we all tried to update when the update notification for 1.10 showed up
i'm guessing we all tried to update when the update notification for 1.10 showed up
Fair, fells odd no one updated or installed manually since the update was released, 8 days ago, and acknowledged the issue.
Same for me on Win 11 (21H2 22000.527)
https://github.com/Foundry376/Mailspring/releases
Reverting to 1.9.2 restored the app.
Why did they push the update if they already knew it had a problem?
I had the same issue on Windows 10 after upgrading. Even purging the database and clean installing caused the issue to happen again. Will be downgrading in the meantime. Update: I downgraded to 1.9.2 but whenever I close Mailspring it auto-updates and breaks again. Gah.
Same issue, fully removed and re-install but still that problem.
Why did they push the update if they already knew it had a problem?
Clearly they didn't test it on a windows machine, only macOS.
Thanks for reporting this. I will take a look and try to resolve this as fast as possible.
Please try to keep this issue clean by not posting "I have this issue too" comments, but only use it to add further information regarding the cause of the issue such as log files.
Had a quick look at the commits, https://github.com/Foundry376/Mailspring/commit/445546f9edb862d60961db8836305507aaa105a5 bumps sqlite version, perhaps this is what breaks it ? I am not familiar with the project, I tried to clone it to test but I fail to build it.
Likewise here - on Windows 11 64 bit
add further information regarding the cause of the issue such as log files.
Hi, I'm not sure which logs are relevant but I'll upload some if they can be useful
mailsync-8f43f2bf.log mailsync-f67fb34f.log mailsync-3baaf1c1.log
Thanks for reporting this. I will take a look and try to resolve this as fast as possible.
Please try to keep this issue clean by not posting "I have this issue too" comments, but only use it to add further information regarding the cause of the issue such as log files.
Question:
What's the windows background service called that keeps Mailspring alive? For now, getting out of the recurring pop-up feedback loop would help.
For now, getting out of the recurring pop-up feedback loop would help.
I kept killing it in the task manager and it finally died after the third or fourth time.
Same for me on Windows 11 (21H2 22000.527)
https://github.com/Foundry376/Mailspring/releases
Reverting to 1.9.2 restored the app.
Idem
I was getting this too, on win11, I was able to launch the old version from this folder for now
Thanks! This enables me to continue using Mailspring
Same issue here. Is the an instruction how to revert back to 1.9.2?
@MauriceNimma you just have to download the old installer from here : https://github.com/Foundry376/Mailspring/releases/tag/1.9.2
Question:
What's the windows background service called that keeps Mailspring alive? For now, getting out of the recurring pop-up feedback loop would help.
For me, killing the Mailspring process when the popup is open did the job.
achievement unlocked
break production database for thousands ( millions??) of users
@primski your data is safe if you didn't delete it manually. This update just make it incompatible with old database I think. If you switch back to old version you recover everything.
Same here.
I reinstalled, deleted the folder, reinstalled it again. It doesn't work.
I managed to download an older version here: https://github.com/Foundry376/Mailspring/releases/tag/1.9.2
This version works, now I have to ignore the update message ;)
As far as I'm aware, there have been problems with better_sqlite3 when cross compiling. I suggest that maybe, for the past releases, no upgrade of better_sqlite3 meant no new compilation and therefore no error, whereas the upgrade now lead to a new compilation that now causes that.
Has the release been cross compiled or natively on Windows? If the former is the case, probably just give compiling from Windows a try.
PS: Seriosly, please stop the "Same here" comments, they aren't helpful.
PPS: Installing 1.9.2 over 1.10 fixes the issue, as previously mentioned. Also works via winget:
winget install --force mailspring --version 1.9.2
same, what a coincidence I found this literally just now from google
I have the same issue on two windows machines. I am really looking forward to use mailspring again. The best mail client I have ever used :)
Stop mailspring
Remove the folder app-1.10.0
in C:\Users\user\AppData\Local\Mailspring
And restart your OS
I am having the same issue on windows 10 as well with 1.10 version. I reinstalled 1.9.2. until the issue has resoved.
Same for me on W7......but you guys tested this update before release it?! i Try on w7 and w10 and same error.....where you installed this update to not show this error?
I am having the same issue on windows 10 as well with 1.10 version. I reinstalled 1.9.2. until the issue has resoved.
Look in your user folder ..\AppData\Local\Mailspring
And remove this folder app-1.10.0
I am having the same issue on windows 10 as well with 1.10 version. I reinstalled 1.9.2. until the issue has resoved.
Look in your user folder
..\AppData\Local\Mailspring
And remove this folderapp-1.10.0
yes but before kill every process mailsping.exe from task manager or it will be impossible remove the 1.10 folder. Do that for remove mailspring loop message windows too.
I am having the same issue on windows 10 as well with 1.10 version. I reinstalled 1.9.2. until the issue has resoved.
Look in your user folder
..\AppData\Local\Mailspring
And remove this folderapp-1.10.0
yes but before kill every process mailsping.exe from task manager or it will be impossible remove the 1.10 folder. Do that for remove mailspring loop message windows too.
Yer right. It's why in my first intervention i asked to Stop mail spring. But it seems that there is another process i can't found. So you can juste restart your computer in case you have no other choice
Also delete the MailSpring folder from Roaming
folder
EDIT. Still not working
Another question: Is there a way to prevent updates?
--> Rename "Update.exe" (stored in C:\Users...\AppData\Local\Mailspring) to "Update.exe_" or anything else :) to prevent running in the same issue again and again.
If anyone knows another solution, please reply
i trust if i skip this update (and by skip i mean already upgraded) and wait until the next one, the problem will be solved?
Same errors here. Downgrade to 1.9.2 in windows 11 fix the problem for now. When they will fix this incompatibility?
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.
Especially since it keeps re-downloading the update since there's no way to disable or postpone updates in the software.
On Mar 9 2022, at 6:29 am, Josias Matschulat @.***> 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. — Reply to this email directly, view it on GitHub @./0?redirect=https%3A%2F%2Fgithub.com%2FFoundry376%2FMailspring%2Fissues%2F2373%23issuecomment-1062977737&recipient=cmVwbHkrQUtGTURSWE9ITkQ3RFNJRTNaT0xRTzZBR1hXRExFVkJOSEhFS1dMTzdZQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe @./1?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKFMDRRCQ5G34ZELKVWH6ODU7CYTLANCNFSM5QIN37NQ&recipient=cmVwbHkrQUtGTURSWE9ITkQ3RFNJRTNaT0xRTzZBR1hXRExFVkJOSEhFS1dMTzdZQHJlcGx5LmdpdGh1Yi5jb20%3D). Triage notifications on the go with GitHub Mobile for iOS @./2?redirect=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&recipient=cmVwbHkrQUtGTURSWE9ITkQ3RFNJRTNaT0xRTzZBR1hXRExFVkJOSEhFS1dMTzdZQHJlcGx5LmdpdGh1Yi5jb20%3D) or Android @./3?redirect=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&recipient=cmVwbHkrQUtGTURSWE9ITkQ3RFNJRTNaT0xRTzZBR1hXRExFVkJOSEhFS1dMTzdZQHJlcGx5LmdpdGh1Yi5jb20%3D). You are receiving this because you are subscribed to this thread.
Rename "Update.exe" (stored in ...\AppData\Local\Mailspring) to "Update.exe_" or anything else :) to prevent running in the same issue again and again.
Having the same problem here ^^
Same here. Ran Mailspring.exe from command line with --mode=migrate as per an old post and got this stack trace, if it's helpful.
I've tried to manually reinstall better-sqlite3 by removing all the packages and installing with npm install <all packages that were in the folder>
it did not change anything
Even if you roll back to the old version, Mailspring will still forcibly install the latest broken update upon next program launch via default launcher. You have to keep launching the executable directly from the app-1.9.2
folder to bypass the forced update. Great product design 👏
I have this issue after upgrading. I have uninstalled the application a few times and deleted the local storage.
All the attempts haven't yielded any good result.
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.