-
-
Notifications
You must be signed in to change notification settings - Fork 119
Description
Core 2.42.0.
Got this device message:
"❌ Failed to receive a message: Message Msg#989113 does not exist. Core version v2.42.0. Please report this bug to delta@merlinux.eu or https://support.delta.chat/."
The log shows that it is a post-message:
2026-02-19T14:41:17.553Z core/event INFO "" 683 "src/receive_imf.rs:537: Receiving message \"76ca7eb5-d919-40c3-9860-404a119aeec3@localhost\", seen=false..."
2026-02-19T14:41:17.553Z core/event INFO "" 683 "src/receive_imf.rs:1284: Message 76ca7eb5-d919-40c3-9860-404a119aeec3@localhost is a post-message (pre-message exists already, so trash after replacing attachment)."
2026-02-19T14:41:17.556Z core/event DEBUG "" 683 "MsgsChanged" {"chatId":1969,"kind":"MsgsChanged","msgId":989112}
2026-02-19T14:41:17.556Z renderer/stores/MessageListStore DEBUG "" "DC_EVENT_MSGS_CHANGED" "changed message seems to be message we already know"
2026-02-19T14:41:17.556Z core/event DEBUG "" 683 "ChatlistChanged" {"kind":"ChatlistChanged"}
2026-02-19T14:41:17.557Z renderer/helpers/ChatList DEBUG "" "useChatList: ChatlistChanged, will refetch chatlist"
2026-02-19T14:41:17.557Z core/event DEBUG "" 683 "ChatlistItemChanged" {"chatId":1969,"kind":"ChatlistItemChanged"}
2026-02-19T14:41:17.557Z renderer/helpers/ChatList DEBUG "" "useChatList: query params are initial, we'll use the cached version of the chat list"
2026-02-19T14:41:17.565Z core/event INFO "" 683 "src/receive_imf.rs:2344: Message has 1 parts and is assigned to chat #Chat#Trash."
2026-02-19T14:41:17.565Z renderer/helpers/ChatList DEBUG "" "useChatList: fetching chatlist"
2026-02-19T14:41:17.569Z renderer/stores/MessageListStore DEBUG "" "messageChanged changed the state"
2026-02-19T14:41:17.569Z core/event WARNING "" 683 "src/imap.rs:1378: receive_imf error: Message Msg#989113 does not exist."
I have 160 KB limit configured, so it was possibly downloaded as a result of manually clicking "Download" on the message.
If there is no idea how to reproduce it, we need to improve the logging inside of receive_imf and reveiew places where messages are loaded to use Message::load_from_db_optional where it is possible that message may already be deleted.
I got this error on desktop, so it is not related to any possible concurrency e.g. on iOS due to having multiple processes accessing the database.
Maybe what happened is that I got pre-message, deletion request for the message and then post-message for the already deleted message.