Skip to content

fix(omemo): silence 'no key' error for key transport messages#2171

Merged
jubalh merged 1 commit into
masterfrom
fixomemo
Jun 2, 2026
Merged

fix(omemo): silence 'no key' error for key transport messages#2171
jubalh merged 1 commit into
masterfrom
fixomemo

Conversation

@jubalh

@jubalh jubalh commented Jun 2, 2026

Copy link
Copy Markdown
Member

Key transport messages (OMEMO messages without a payload) are used for background synchronization and may not include a key for every device a user owns.

This change ensures that OMEMO_ERR_KEY_TRANSPORT (which is silenced by the UI) is returned if no key is found and there is no payload, identifying the message as a background sync not intended for this specific device.

Ref: a824b26
Ref: 1458b09

Key transport messages (OMEMO messages without a payload) are used for
background synchronization and may not include a key for every device
a user owns.

This change ensures that OMEMO_ERR_KEY_TRANSPORT (which is silenced
by the UI) is returned if no key is found and there is no payload,
identifying the message as a background sync not intended for this
specific device.

Ref: a824b26
Ref: 1458b09
Signed-off-by: Michael Vetter <jubalh@iodoru.org>
@jubalh jubalh added this to the next milestone Jun 2, 2026
@jubalh jubalh self-assigned this Jun 2, 2026
@jubalh jubalh merged commit 73ef0b6 into master Jun 2, 2026
12 checks passed
@jubalh jubalh deleted the fixomemo branch June 2, 2026 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant