nextcloud / nextcloud/talk-android
Incorrect avatar placement causing author confusion
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
Android users have been complaining of incorrect avatars causing confusion. Sometimes avatar is not showing up in the right place, causing comments to appear to be written by someone else.
Not sure how to reproduce, problem is intermittent. Restarting app will fix it.
Expected behaviour
Avatar should consistently display along with users first comment in a series, otherwise it appears to be attributed to the previous comment author.
Actual behaviour
Including screenshots to demonstrate. One shows the issue occurring, the other is after restarting the app and it displays correctly.
Device brand and model
Multiple, can identify if needed
Android version
Multiple, ongoing issue for a while. Can identify if needed.
Nextcloud Talk app version
22.0.3 and earlier
Nextcloud server version
32.0.3
Talk version
22.0.7
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
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
No files, tests, or code entry points are identified. Start by reproducing the intermittent avatar placement issue on Android with Talk 22.0.7 and server 32.0.3, using the provided screenshots as the expected comparison; gather device details and logs if possible. Done means avatars consistently appear with the first comment in each user's series without requiring an app restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100