nextcloud / nextcloud/talk-android
No notification sound for new messages when there already are unread messages
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- On phone A send message to phone B.
- Notification appears on phone B. Notification sound is played.
- Don't read the message on phone B.
- Send another message from phone A to phone B.
- The message text is appended to an old notification. No notification sound is played.
Expected behaviour
Notification sound should play every time a new message is recieved. This is the way it works on other messaging apps, so this is the expected behaviour. For preventing sound flood a 10 second delay could be set before allowing new notification sounds.
Actual behaviour
No notification sound is played, so if the person has missed the first notification, it is impossible to get their attention by sending another message.
Device brand and model
Any
Android version
11
Nextcloud Talk app version
17.1.0
Nextcloud server version
27.1.0
Talk version
17.1.1
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the notification flow on Android 11 with unread messages, using the listed Talk app and server versions. Trace the notification handling entry point and determine why appended notifications do not play a sound; done means each new message produces a sound while respecting any agreed delay, with regression coverage where the existing notification behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100