Encrypted chats fail to restore

[shioprince]

Describe the bug
When I try to restore encrypted chats on Commet, both via recovery key or verifying sessions via another session, they fail to decrypt/restore.

To Reproduce
Attempt to recover encrypted chats via either recovery key or verifying sessions, and watch them still fail to decrypt.

Expected behavior
The chats restore like normal.

Screenshots

This is after I tried to recover my encrypted chats via my recovery key.

Additional context
I am using the unredacted.org homeserver, not sure if that's relevant or not.

Device Information

Device
Platform: web
Version: v0.4.1
Git Hash: c2ee370d18c822673b24b6579842a01b971b1584
Detail: default
Build Timestamp: 1772620983683 (March 4, 2026)

System Info

Product: Gecko

[DeMuenu]

I have the same problem. I figured out that if you log in to a new device and immediately open settings and set your recovery key, the messages decrypt normally. If you open an encrypted chat while not yet having provided a key, then that chat will fail to decrypt even after providing a key.

@shioprince temporary fix is to immediately provide your key in the settings after logging in without opening any chat.

[Dark-Sheepa]

I agree that currently, the restoration is still in its infancy, because sometimes I have to do three reinstallations or several logouts and logins and imports before everything unlocks. Currently, all of this is possible, but it's not a desirable first experience for newcomers. This is currently the most common question I get from people about the Commet.

[GravityEcho]

similar to #798

[masonlogan1]

I am experiencing this on mobile, but only when I close and reopen Commet. I have the app saved as a PWA and if I close and open it, all of my messages are no longer able to be decrypted. Because phones eventually close apps in the background, I can go a maximum of around a day and a half before I have to completely log out, log in, and perform the verification.

It seems like the issue is that on some devices, in the web version, the keys are either not being persisted or are not being loaded whenever the application completely closes.

Device
Platform: web
Version: v0.4.1
Git Hash: c2ee370d18c822673b24b6579842a01b971b1584
Detail: default
Build Timestamp: 1772620983683 (March 4, 2026)

System Info
Product: Gecko

[TomatoLoli]

Can confirm. Same issue for myself.

Device Information

Device
Platform: linux
Version: v0.4.1
Git Hash: c2ee370d18c822673b24b6579842a01b971b1584
Detail: flatpak
Build Timestamp: 1772620823192 (March 4, 2026)

System Info
Name: GNOME
Version: 48 (Flatpak runtime)

Display Server: wayland
Desktop Environment: wayland