Chats with only unreadable encrypted messages are missing from the chat list #26

New issue

Closed

opened 2026-10-17 21:15:44 +00:00 by bmt · 1 comment

bmt commented

2026-10-17 21:15:44 +00:00

Member

build: anotherim-js 0.6.0 (Windows)

A chat whose messages can't be decrypted on this device is not shown in the chat list, even after opening it. It appears only after a readable message

steps:

Sign in on a new device to an account with OMEMO chats
Account menu → Contacts → open a contact
Look at the chat list

expected: every chat with messages is in the chat list

actual: chats with only unreadable messages are missing

build: anotherim-js 0.6.0 (Windows) A chat whose messages can't be decrypted on this device is not shown in the chat list, even after opening it. It appears only after a readable message steps: 1. Sign in on a new device to an account with OMEMO chats 2. Account menu → Contacts → open a contact 3. Look at the chat list expected: every chat with messages is in the chat list actual: chats with only unreadable messages are missing

bmt added the

bug

windows

ui/ux

labels

2026-10-17 21:15:44 +00:00

ann referenced this issue from a commit

2026-10-18 10:26:07 +00:00

0.6.1, on libtacky v1.0.1 (22d95f56): the changelog's Unreleased section becomes 0.6.1, dated today and naming libtacky 1.0.1, with the two libtacky fixes it gains (a device signed in later gets the account's synced pins, drafts and settings; chats this device cannot read are listed, #26) and the NVIDIA-under-Wayland start; the metainfo's 0.6.1 release (appstreamcli validate clean); version 0.6.1 in ui/package.json and its lock, tauri.conf.json, Cargo.toml and Cargo.lock, and the README; the submodule is at the tag.

ann commented

2026-10-18 10:35:24 +00:00

Owner

The chat list dated a chat only by its newest readable message, and history that couldn't be decrypted never told the list. A chat holding only unreadable messages is now listed and dated by its newest one, after the catch-up and after opening it (libtacky 1.0.1).

Fixed in 0.6.1: https://dev.another.im/another-im/anotherim-js/releases/tag/v0.6.1

ann closed this issue

2026-10-18 10:35:24 +00:00