Open capi1O opened 7 years ago
I'm experiencing the same issues with my fastmail account.
I have the same issue, pretty much same config.
ChangeUnreadTask (ID: aa0b) FAILED (PROCESSING REMOTE) APIError 500 All messages in a thread require an IMAP uid to perform an action
{
"_rememberedToCallSuper": true,
"id": "local-8329828f-aa0b",
"sequentialId": 1488977621799,
"queueState": {
"isProcessing": false,
"localError": null,
"localComplete": true,
"remoteError": {
"stack": "Error\n at new APIError (/src/flux/errors.es6:29:19)\n at _actions2.default.didReceiveSyncbackRequestDeltas.listen.syncbackRequests (/src/flux/syncback-task-api-request.es6:29:25)\n at EventEmitter.eventHandler (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:36:22)\n at EventEmitter.emit (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/eventemitter3/index.js:72:35)\n at Function.trigger (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/reflux/src/PublisherMethods.js:52:26)\n at Function.functor [as didReceiveSyncbackRequestDeltas] (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/reflux/src/createAction.js:32:56)\n at DeltaProcessor._notifyOfSyncbackRequestDeltas (/internal_packages/deltas/lib/delta-processor.es6:142:13)\n at /internal_packages/deltas/lib/delta-processor.es6:80:12\n at next (<anonymous>)\n at step (/internal_packages/deltas/lib/delta-processor.es6:2:1)\n at /internal_packages/deltas/lib/delta-processor.es6:2:1\n at tryCatcher (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/util.js:16:23)\n at Promise._settlePromiseFromHandler (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:510:31)\n at Promise._settlePromise (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:567:18)\n at Promise._settlePromiseCtx (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:604:10)\n at Async._drainQueue (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/async.js:138:12)\n at Async._drainQueues (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/async.js:143:10)\n at Immediate.Async.drainQueues (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/async.js:17:14)\n at tryOnImmediate (timers.js:554:5)\n at processImmediate [as _immediateCallback] (timers.js:533:5)",
"name": "APIError",
"error": {
"stack": "Error: All messages in a thread require an IMAP uid to perform an action\n at NylasError (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/isomorphic-core/src/errors.js:2:1)\n at APIError (/Applications/Nylas Mail.app/Contents/Resources/app.asar/node_modules/isomorphic-core/src/errors.js:18:5)\n at Object.forEachFolderOfThread (/Applications/Nylas Mail.app/Contents/Resources/app.asar/internal_packages/client-sync/src/local-sync-worker/imap-helpers.js:16:13)\n at MarkThreadAsRead.run (/Applications/Nylas Mail.app/Contents/Resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/mark-thread-as-read.imap.js:26:23)",
"message": "All messages in a thread require an IMAP uid to perform an action"
},
"body": {
"message": "All messages in a thread require an IMAP uid to perform an action"
},
"requestOptions": null,
"statusCode": 500,
"message": "All messages in a thread require an IMAP uid to perform an action"
},
"remoteAttempts": 1,
"remoteComplete": false,
"status": "FAILED",
"debugStatus": "PROCESSING REMOTE"
},
Thanks! We're looking into this one
In my case, I experience the issue when one of the mails in the thread is duplicated (see attached image, last two elements are the same, duplicated). I cannot archive nor delete the thread, and even if I archive it in Gmail web and reload, the thread is still there, unread. This duplication happens sporadically, hard to reproduce.
I'm experiencing the same as @druizz. I have a duplicate email in the thread. I got rid of it via gmail and it still shows, but I've only had this happen on one thread.
I have the same thing happen, but it's only ever with one contact. It's happening almost every day lately. To fix it, I've been deleting the app cache and reinstalling but that's annoying as hell to do every day.
This should be fixed in our latest release!
@jstejada big thanks! :+1:
I have 2.0.10 installed and still face the issue. @jstejada , is it supposed to be fixed with this release or is it in a next one? Thanks!
I'm experiencing this issue with Nylas 2.0.15 when I attempt to un-star messages — this is with a Fastmail account.
@bongoman can you easily reproduce this issue (star, un-star messages) or does this only happen occasionally? In case it only happens occasionally, it may be worth resetting your Email cache.
Nylas Mail > General > Reset Email Cache
Reopening given that there are still reports. We're looking into it!
Yes I have exactly this issue on 2.0.15 on MacOS Sierra 10.12.4 using solely Gmail accounts.
I have the same error on a normal IMAP account using Nylas 2.0.16 on Windows 7.
same issue, Imap account, 2.0.16, windows 10
same issue, GMail, 2.0.18, linux, official deb build
log:
{
"host":"myhost",
"timestamp":"2017-04-25T12:40:34.700Z",
"payload":{
"fingerprint":[
"{{ default }}",
"syncback task",
"All messages in a thread require an IMAP uid to perform an action"
],
"pluginIds":[
"client-sync"
]
}
}
{
"host":"myhost",
"timestamp":"2017-04-25T12:40:34.715Z",
"payload":"Error: All messages in a thread require an IMAP uid to perform an action\n at NylasError (errors.es6:1:8)\n at APIError (errors. es6:17:5)\n at Object.forEachFolderOfThread (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/imap-helpers.js:16:13)\n at /internal_packages/client-sync/src/ local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.es6:41:23\n at next (<anonymous>)\n at resume (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync- worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3:448)\n at /usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3:367\n at Promise._execute (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/debuggability.js:300:9)\n at Promise._resolveFromExecutor (/usr/share/nylas-mail/resources/ app.asar/node_modules/bluebird/js/release/promise.js:481:18)\n at new Promise (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/promise.js:77:14)\n at AsyncGenerator.send [as _invoke] (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3:169)\n at advance (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/shared/interruptible.js:78:31)\n at err (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/shared/interruptible.js:110:17)"
}
{
"host":"myhost",
"timestamp":"2017-04-25T12:40:34.715Z",
"payload":{
"rateLimit":{
"ratePerHour":30,
"key":"UnhandledRejection:Error: All messages in a thread require an IMAP uid to perform an action\n at NylasError (errors.es6:1:8)\n at APIError (errors.es6:17:5)\n at Object.forEachFolderOfThread (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/imap-helpers. js:16:13)\n at /internal_packages/client-sync/src/local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.es6:41:23\n at next (<anonymous>)\n at resume (/usr/share/nylas-mail/resources/app. asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3:448)\n at /usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync- worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3:367\n at Promise._execute (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/debuggability.js:300:9)\n at Promise. _resolveFromExecutor (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/promise.js:481:18)\n at new Promise (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/ promise.js:77:14)\n at AsyncGenerator.send [as _invoke] (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/set-thread-folder-and-labels.imap.js:3: 169)\n at advance (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/shared/interruptible.js:78:31)\n at err (/usr/share/nylas-mail/resources/app.asar/internal_packages/client- sync/src/shared/interruptible.js:110:17)"
},
"pluginIds":[
"client-sync"
]
}
}
Same issue, MacOS, Rackspace email.
Same issue, even after updating to yesterday's release (2.0.28). MacOS Sierra 10.12.4, G-Suite
"Error We were unable to apply the changes to your thread, please try again later. Error message: All messages in a thread require an IMAP uid to perform an action"
Sam issue. MacOS Sierra 10.12.4, G-Suite
I think that this is actually caused (for me, at least) on the initial sync of my account (which has been going for 24 hours on my account, but there are a lot of emails in there). I've noticed that, as folders sync, it then lets me move things around without issue (I have one email left that still gives me the error).
On Thu, Apr 27, 2017 at 8:01 PM tongnk notifications@github.com wrote:
Sam issue. MacOS Sierra 10.12.4, G-Suite
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nylas/nylas-mail/issues/3308#issuecomment-297871458, or mute the thread https://github.com/notifications/unsubscribe-auth/AFwWbm6IGsoFzhhvvOIAg0w2OYmwVM30ks5r0Sw7gaJpZM4MQwe9 .
Quick Fix: Remove email account with the problem through the preference panel and re-add the account. After the initial sync, the problem disappeared.
Count me in. Linux release, v2.0.32, with a Fastmail account. Happened in earlier versions as well.
Hi there, I just started using Nylas mail on friday, and encountered this bug today. Any news on a fix?
Same here with v2.0.32 on Fedora and an IMAP account.
Same on Ubuntu 17.04, Nylas version 2.0.31
Here is the error message from the log:
{"host":"comp_name","timestamp":"2017-05-09T09:36:55.012Z","payload":"Error: All messages in a thread require an IMAP uid to perform an action\n at NylasError (errors.es6:1:8)\n at APIError (errors.es6:17:5)\n at Object.forEachFolderOfThread (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/imap-helpers.js:16:13)\n at /internal_packages/client-sync/src/local-sync-worker/syncback-tasks/mark-thread-as-read.imap.es6:26:23\n at next (<anonymous>)\n at resume (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/mark-thread-as-read.imap.js:3:448)\n at /usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/mark-thread-as-read.imap.js:3:367\n at Promise._execute (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/debuggability.js:300:9)\n at Promise._resolveFromExecutor (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/promise.js:481:18)\n at new Promise (/usr/share/nylas-mail/resources/app.asar/node_modules/bluebird/js/release/promise.js:77:14)\n at AsyncGenerator.send [as _invoke] (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/local-sync-worker/syncback-tasks/mark-thread-as-read.imap.js:3:169)\n at advance (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/shared/interruptible.js:78:31)\n at err (/usr/share/nylas-mail/resources/app.asar/internal_packages/client-sync/src/shared/interruptible.js:110:17)"}
Let me know if you need the whole log.
Still a problem for me too.
MacOS Sierra 10.12.5 Nylas 2.0.32
Only one thread, last two emails in the thread are duplicates. Shows as archived in Gmail and not duplicate message.
I'm still getting this with a single FastMail account. NixOS 17.03, Nylas 2.0.32.
Happening to me as of today Nylas 2.0.31 on Fedora using an IMAP account.
Happening to me as well with Windows 10 Pro 1703, Nylas 2.0.32, using Fastmail.
Happening to me with Kubuntu 17.10 and Nylas 2.0.32 using IMAP account.
This continuing to happen to me. 6 emails total... 4 of which were in the last 2 days. If it helps.. this seems to only be happening when I send an email with my company email alias cc'd (think support@). Support emails also go to in my inbox. So whenever I send an email with support@ cc'd, it goes into my inbox as a new message, and that's when the chain gets flagged with this error.
reacting on @Melissa-Kay 's message: I can't figure out a pattern on my side. I have one account and it seems to happen randomly. It worked fine this morning, and now the issue shows up again this afternoon.
I have the same issue with 2.0.31
and gmail.
Archive and delete won't work I am able to do this actions from the gmail client.
Happen to me as well.
operating system : Mac - Sierra OS 10.12.3 Nylas Mail version : v2.0.32 (2.0.32) third-party plugins installed : Jiffy, Honeyduke, n1-firefox-theme issue related to a specific email provider : happens with fastmail (IMAP). issue reproducibility : just happen with the Fastmail server, not with google.
I have the same issue as well..
Operating system - Mac Sierra OS 10.12.5 Nylas Mail version - v2.0.32 (2.0.32) Third-party plugins installed - n1-avatars, Taiga theme Issue related to a specific email provider - Office(ActiveExchange) IMAP acct.
same thing here. nylas v2.0.32 latest sierra
Ubuntu 16.04 x64 Nylas 2.0.32. Also on Windows 10 x64.
A workaround for IMAP which I found works for me : add another post in the thread (like forwarding it to yourself) and then the email can be handled (moved, deleted, archived,..) again.
Same thing here. Nylas 2.0.32, Sierra 10.12.1, Fastmail
Same here on Nylas 2.0.32 (Sierra). Amazed this is not resolved for paying users fast, kind of ignorant - renders the client so buggy I thinking of swtiching.
Agreed w/ @grimen -- it's been three months. Would love to at least see an update from the Nylas team. I've switched away because this issue is so painful.
@kareem I concur, I was initially really excited about the project but the lack of support lately has meant I've decided to cease assisting the project as a paying user. I had been paying the past few months even though there was no extra functionality for paying users because I like the project, but it has been unusable for me since this problem.
I've moved back to trusty Thunderbird where at least I can send messages. Maybe I'll switch back in the future if the project returns to being supported.
Started using Nylas, really like the gui but this issue is really painful. Is it ever going to be fixed? Can't see myself paying for the service with this bug outstanding.
I confirm this bug with Nylas Mail version 2.0.32 on Xubuntu 16.04 LTS.
Also experiencing this issue on Nylas 2.0.32 on macOS Sierra 10.12.5.
In my case:
GNU/Linux ubuntu 17.04
helped that:
sudo apt-get install
and (re)installing the newest version of Nylas Mail v2.0.32: Download Nylas .deb v2.0.32
Experiencing this issue on Nylas 2.0.32 on Windows Version 10.0.15063 Build 15063, with a gmail account, seems to have been triggered by any conversation thread, giving the following error:
Got issue on Nylas 2.0.32 on macOS Sierra 10.12.6, on a GSuite account. NylasMail > Preferences > General > Reset Email Cache resolved the issue for me.
Any updates on this issue? I really don't want to switch email client but now this issue is becoming annoying.
I've switched to Astro. It's faster, cleaner, and much better supported than Nylas.
I have an error with two custom IMAP accounts (mail.com and OVH), some emails cannot be marked as read. I have seen another issue related to mark as read problems (https://github.com/nylas/nylas-mail/issues/1298) however this is different as even after changing view or directory I still cannot mark the email as read. I have also seen the issue about sync problems (#781) but it has been closed.