nextcloud / nextcloud/talk-android
"Guest is typing" instead of User in direct chat?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps to reproduce
- User A starts a direct conversation to user B
- User A starts typing
- Switch to user B
Expected behaviour
User B should see "User A" is typing.
Actual behaviour
User B sees "Guest is typing"
Device brand and model
Google Pixel 8 Pro
Android version
15
Nextcloud Talk app version
22.0.2
Nextcloud server version
No response
Talk version
No response
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
Additional information
This issue happens randomly.
It could be that this is a fallback where a typing message was received, but the app did not know the display name of the user yet?
So it could be a race condition?
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 direct-chat typing indicator using the listed steps on the reported Android setup, then trace how typing events and user display names are handled. Done means the recipient consistently sees the sender's name instead of "Guest", including when the issue's suspected race condition occurs.
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
- 35/100