Mailspring encountered an error while syncing

Description

Mailspring encountered an error while syncing my gmail account every time I open it - My OS is ubuntu 20.04

This is the exception:


*** Mailspring Sync
*** A C++ exception occurred during program execution:
*** UNIQUE constraint failed: Thread.id


To Reproduce…

Just open Mailspring

Expected Behavior

sync email

Screenshots

Setup

OS is ubuntu 20.04
Mailspring Version: 1.9.2-6e14dad1
Platform: linux
Account State: sync_error
Account Provider: gmail
IMAP Server: imap.gmail.com
SMTP Server: smtp.gmail.com

Additional Context


9426 [2021-12-07 07:53:12.324] [metadata] [info] Metadata delta stream starting…
9426 [2021-12-07 07:53:16.322] [background] [info] Fetching XOAuth2 access token (gmail) for ba5b9745
9426 [2021-12-07 07:53:16.542] [background] [info] Marking all folders as busy
9426 [2021-12-07 07:53:16.546] [background] [info] Syncing folder list…
9426 [2021-12-07 07:53:18.714] [background] [info] Syncing folder list…
9426 [2021-12-07 07:53:19.627] [background] [info] syncFolderUIDRange for [Gmail]/Lixeira, UIDs: 17656 - 17675, Heavy: true
9426 [2021-12-07 07:53:20.255] [background] [info] - remote=18, local=17
9426 [2021-12-07 07:53:20.264] [background] [warning] Ignoring changes to Alerta de segurança, local data is newer 1638874399 < 1638898454
9426 [2021-12-07 07:53:20.265] [background] [info] syncFolderUIDRange for [Gmail]/Lixeira, UIDs: 1 - 17675, Heavy: false
9426 [2021-12-07 07:53:20.613] [background] [info] - remote=263, local=303
9426 [2021-12-07 07:53:20.614] [background] [info] - Fetching full headers for 2 (of 2 needed)
9426 [2021-12-07 07:53:20.905] [background] [warning] Ignoring changes to Alerta de segurança, local data is newer 1638874400 < 1638898454
9426 [2021-12-07 07:53:20.909] [background] [critical]


*** Mailspring Sync
*** A C++ exception occurred during program execution:
*** UNIQUE constraint failed: Thread.id


9446 [2021-12-07 07:53:21.127] [main] [info] Identity created at 1601357748 - using ID Schema 1
9446 [2021-12-07 07:53:21.128] [main] [info] ------------- Starting Sync (********@gmail.com) ---------------
9446 [2021-12-07 07:53:21.133] [metadata] [info] Metadata delta stream starting…
9446 [2021-12-07 07:53:25.133] [background] [info] Fetching XOAuth2 access token (gmail) for ba5b9745
9446 [2021-12-07 07:53:25.402] [background] [info] Marking all folders as busy
9446 [2021-12-07 07:53:25.403] [background] [info] Syncing folder list…
9446 [2021-12-07 07:53:28.136] [background] [info] Syncing folder list…
9446 [2021-12-07 07:53:29.048] [background] [info] syncFolderUIDRange for [Gmail]/Lixeira, UIDs: 17656 - 17675, Heavy: true
9446 [2021-12-07 07:53:29.751] [background] [info] - remote=18, local=17
9446 [2021-12-07 07:53:29.760] [background] [warning] Ignoring changes to Alerta de segurança, local data is newer 1638874409 < 1638898454
9446 [2021-12-07 07:53:29.762] [background] [info] syncFolderUIDRange for [Gmail]/Lixeira, UIDs: 1 - 17675, Heavy: false
9446 [2021-12-07 07:53:30.124] [background] [info] - remote=263, local=303
9446 [2021-12-07 07:53:30.125] [background] [info] - Fetching full headers for 2 (of 2 needed)
9446 [2021-12-07 07:53:30.416] [background] [warning] Ignoring changes to Alerta de segurança, local data is newer 1638874410 < 1638898454
9446 [2021-12-07 07:53:30.421] [background] [critical]


*** Mailspring Sync
*** A C++ exception occurred during program execution:
*** UNIQUE constraint failed: Thread.id


Did you install the snap or the deb? Try installing the other. (FWIW, I’ve found the snap to have significantly more problems than the deb.)

I have installed the snap package. I already uninstalled it and installed the deb. Let’s see if it resolves my problem thankyou @JohnP

This is a problem only with the snap package. I installed the .deb, and it works just fine.

Well, I’m glad you’ve got a solution! I do wish they’d fix the snap package, though, given how many people go for that one first. :roll_eyes:

2 Likes

I had the exact same issue on PopOS when using “deb.” Removed the program and re-installed it using PopOS store (it runs its own feeds) and it immediately fixed the issue.