Verify what the placeholder says today for an undecryptable event (DecryptionError codes from matrix-js-sdk rust-crypto: HISTORICAL_MESSAGE_NO_KEY_BACKUP, HISTORICAL_MESSAGE_BACKUP_UNCONFIGURED, HISTORICAL_MESSAGE_WORKING_BACKUP ("key backup is working, but we still do not (yet) have the key"), MEGOLM_KEY_WITHHELD(_FOR_UNVERIFIED_DEVICE), UNKNOWN_SENDER_DEVICE, UNSIGNED_SENDER_DEVICE, MEGOLM_UNKNOWN_INBOUND_SESSION_ID).
Scope
Map each code to one sentence + one action button, rendered inside the existing placeholder (no modal): backup unconfigured → Set up key backup; backup working but key not yet there → "Waiting for key backup… " with Retry; key withheld for unverified device → Verify this session; unknown inbound session → Request key from my other devices (crypto.requestRoomKey / re-request); sender-side problems → plain text, no button.
Never expose raw codes to users (keep them in the tooltip for support / Crypto Diagnostics).
Unit-test the code→copy/action mapping (utils/decryptionReason.ts).
Verify what the placeholder says today for an undecryptable event (`DecryptionError` codes from matrix-js-sdk rust-crypto: `HISTORICAL_MESSAGE_NO_KEY_BACKUP`, `HISTORICAL_MESSAGE_BACKUP_UNCONFIGURED`, `HISTORICAL_MESSAGE_WORKING_BACKUP` ("key backup is working, but we still do not (yet) have the key"), `MEGOLM_KEY_WITHHELD(_FOR_UNVERIFIED_DEVICE)`, `UNKNOWN_SENDER_DEVICE`, `UNSIGNED_SENDER_DEVICE`, `MEGOLM_UNKNOWN_INBOUND_SESSION_ID`).
### Scope
- Map each code to one sentence + one action button, rendered inside the existing placeholder (no modal): backup unconfigured → *Set up key backup*; backup working but key not yet there → "Waiting for key backup… " with *Retry*; key withheld for unverified device → *Verify this session*; unknown inbound session → *Request key from my other devices* (`crypto.requestRoomKey` / re-request); sender-side problems → plain text, no button.
- Never expose raw codes to users (keep them in the tooltip for support / Crypto Diagnostics).
- Unit-test the code→copy/action mapping (`utils/decryptionReason.ts`).
Verified first: the placeholder was the bare "Unable to decrypt message" for every code. Done in 0e267189:
utils/decryptionReason.ts maps every DecryptionFailureCode to one sentence + at most one action (unit test iterates the whole enum and asserts no raw code or code-like text in the copy):
HISTORICAL_MESSAGE_NO_KEY_BACKUP → "…no key backup exists — set one up so your next session can read history." → Set up key backup
HISTORICAL_MESSAGE_BACKUP_UNCONFIGURED → "Your key backup exists but this session can't open it yet." → Unlock key backup
HISTORICAL_MESSAGE_WORKING_BACKUP → "Waiting for the key from your backup…" → Retry
MEGOLM_KEY_WITHHELD_FOR_UNVERIFIED_DEVICE → Verify this session
MEGOLM_UNKNOWN_INBOUND_SESSION_ID / OLM_UNKNOWN_MESSAGE_INDEX → "…it is being requested from your other devices." → Retry (rust-crypto has no public re-request API — it re-requests by itself; Retry re-runs decryptEventIfNeeded)
USER_NOT_JOINED, KEY_WITHHELD, SENDER_IDENTITY_PREVIOUSLY_VERIFIED, UNSIGNED_SENDER_DEVICE, UNKNOWN_SENDER_DEVICE → plain text, no button.
The backup/verify buttons open Settings → Devices through a new settingsRequestAtom (any component can now open settings at a page). The raw code lives in the placeholder's tooltip.
Verified first: the placeholder was the bare "Unable to decrypt message" for every code. Done in `0e267189`:
`utils/decryptionReason.ts` maps every `DecryptionFailureCode` to one sentence + at most one action (unit test iterates the whole enum and asserts no raw code or code-like text in the copy):
- `HISTORICAL_MESSAGE_NO_KEY_BACKUP` → "…no key backup exists — set one up so your next session can read history." → **Set up key backup**
- `HISTORICAL_MESSAGE_BACKUP_UNCONFIGURED` → "Your key backup exists but this session can't open it yet." → **Unlock key backup**
- `HISTORICAL_MESSAGE_WORKING_BACKUP` → "Waiting for the key from your backup…" → **Retry**
- `MEGOLM_KEY_WITHHELD_FOR_UNVERIFIED_DEVICE` → **Verify this session**
- `MEGOLM_UNKNOWN_INBOUND_SESSION_ID` / `OLM_UNKNOWN_MESSAGE_INDEX` → "…it is being requested from your other devices." → **Retry** (rust-crypto has no public re-request API — it re-requests by itself; Retry re-runs `decryptEventIfNeeded`)
- `USER_NOT_JOINED`, `KEY_WITHHELD`, `SENDER_IDENTITY_PREVIOUSLY_VERIFIED`, `UNSIGNED_SENDER_DEVICE`, `UNKNOWN_SENDER_DEVICE` → plain text, no button.
The backup/verify buttons open Settings → Devices through a new `settingsRequestAtom` (any component can now open settings at a page). The raw code lives in the placeholder's tooltip.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Verify what the placeholder says today for an undecryptable event (
DecryptionErrorcodes from matrix-js-sdk rust-crypto:HISTORICAL_MESSAGE_NO_KEY_BACKUP,HISTORICAL_MESSAGE_BACKUP_UNCONFIGURED,HISTORICAL_MESSAGE_WORKING_BACKUP("key backup is working, but we still do not (yet) have the key"),MEGOLM_KEY_WITHHELD(_FOR_UNVERIFIED_DEVICE),UNKNOWN_SENDER_DEVICE,UNSIGNED_SENDER_DEVICE,MEGOLM_UNKNOWN_INBOUND_SESSION_ID).Scope
crypto.requestRoomKey/ re-request); sender-side problems → plain text, no button.utils/decryptionReason.ts).Verified first: the placeholder was the bare "Unable to decrypt message" for every code. Done in
0e267189:utils/decryptionReason.tsmaps everyDecryptionFailureCodeto one sentence + at most one action (unit test iterates the whole enum and asserts no raw code or code-like text in the copy):HISTORICAL_MESSAGE_NO_KEY_BACKUP→ "…no key backup exists — set one up so your next session can read history." → Set up key backupHISTORICAL_MESSAGE_BACKUP_UNCONFIGURED→ "Your key backup exists but this session can't open it yet." → Unlock key backupHISTORICAL_MESSAGE_WORKING_BACKUP→ "Waiting for the key from your backup…" → RetryMEGOLM_KEY_WITHHELD_FOR_UNVERIFIED_DEVICE→ Verify this sessionMEGOLM_UNKNOWN_INBOUND_SESSION_ID/OLM_UNKNOWN_MESSAGE_INDEX→ "…it is being requested from your other devices." → Retry (rust-crypto has no public re-request API — it re-requests by itself; Retry re-runsdecryptEventIfNeeded)USER_NOT_JOINED,KEY_WITHHELD,SENDER_IDENTITY_PREVIOUSLY_VERIFIED,UNSIGNED_SENDER_DEVICE,UNKNOWN_SENDER_DEVICE→ plain text, no button.The backup/verify buttons open Settings → Devices through a new
settingsRequestAtom(any component can now open settings at a page). The raw code lives in the placeholder's tooltip.