Mailspring: Several of your accounts are having issues syncing

[agurodriguez]

Are there any related issues?

No, AFAIK

What operating system are you using?

macOS Sierra 10.12.6

What version of Mailspring are you using?

1.0.0-20839f9b

--

Bug?

Do you have any third-party plugins installed? If so, which ones?

No

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

iCloud and custom IMAP

---

Several seconds after Mailsprint starts all my accounts stop being synced and this alert appears:

Here is the console output:

And here in plain text:
SyncWorker crashed.txt

Finally the entire console output:
1507056316741.log

[bengotow]

Hey @agurz thanks for reporting this - it looks like you must have an email in your accounts that doesn't have a "header message id". I'm adding some improved error handling that should fix this in the next release. Stay tuned!

[LiHRaM]

Hey. I'm also having trouble syncing accounts that work fine in nylas-mail and nylas-mail-lives.
Is this problem a part of the C++ sync-engine?

Updated: Confirmed no errors on updating to the latest edition. Thank you. :)

[bengotow]

Version 1.0.1 started shipping a few minutes ago, so this should be fixed now. Let me know if you still see this after updating!

[agurodriguez]

Hey! Thanks for bringing this awesome email client back to life! This seems to be fixed, but I'm now experiencing another issue with syncing (I'll open another issue after collecting some more data).

[ghost]

I'm getting this issue.
I'm on Ubuntu 17.10
Have installed mailspring as a snap package and I'm currently using v1.0.12
Please help.

[Edit]
I tried running mailspring in debug mode using "mailspring -d" in terminal
This is the result:
ln: failed to create symbolic link '/home/karenachiketc/snap/mailspring/105/.config/gtk-2.0/gtkfilechooser.ini': File exists
Gtk-Message: Failed to load module "canberra-gtk-module"
Streaming log data to /run/user/1000/snap.mailspring/Mailspring-4334.log
App load time: 358ms

Solution:
I terminated the mailspring background process and follewed this link and then restarted mailspring. It fixed the problem