element-hq / element-hq/element-web

Thread replies sent from Element Android cause neither unread count nor unread dot on Element Desktop

Open
#25,621 2 comments 0 reactions 0 assignees View on GitHub
A-Notifications A-Threads O-Occasional S-Major T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Create a new private & encrypted room (user A / ED)
2. Invite another user (user A / ED)
3. Post a few messages into the room (user A / ED)
4. Start threads on either of the messages (user B / EA)

### Outcome

#### What did you expect?

A notification count > 0 once for user A (ED) once a thread reply was sent by user B (EA)

#### What happened instead?

The room did receive neither an unread count nor an unread dot for user A (ED). The threaded messages are visible when going into the room though.

When a new thread was started by user B (EA), no audible notification was played for user A (ED). However, when user B (EA) sent _another_ message into an existing thread, user A (ED) experienced an audible ping – again, without any unread count or dot though.

### Operating system

macOS

### Application version

Element Desktop nightly

### How did you install the app?

https://packages.element.io/nightly/

### Homeserver

element.io

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.