nextcloud / nextcloud/talk-android
Messages from Matterbridge merged falsely
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- Create a Chatroom in Nextcloud Talk
- Add a Matterbridge bridge
- Start Reading messages provided by bridge-bot on desktop with proper username in the title
- Switch to Talk-Android and see all the messages merged losing the username in the title
Expected behaviour
Talk-Android should keep the usernames of the senders in the message title to make it possible to understand who sent which message.
Actual behaviour
Alle messages are merged losing their username title leaving it appearing as if one user sent all the messages. It somehow works in the desktop version and is only seen in the Android app. Guess It is merely caused by the wrong message meta data used for merging.
Device brand and model
Fairphone 4
Android version
11
Nextcloud Talk app version
15.0.1
Nextcloud server version
24.0.7
Talk version
14.0.6
Custom Signaling server configured
No response
Custom TURN server configured
Yes
Custom STUN server configured
No response
Android logs
None triggered.
Server log
None triggered.
Additional information
None so far.
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 Matterbridge scenario in Talk-Android 15.0.1 with the listed server and app versions, comparing Android with the desktop behavior. Inspect the message metadata used when bridge-bot messages are merged; done when distinct sender usernames remain visible in Android message titles, with a regression check for the reproduced case.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100