nextcloud / nextcloud/talk-android
Immediate back button after "start/join call" results in broken state
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 739
- Forks
- 321
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 151
Description
Steps
- Have a conversation with a slow internet connection
- Go to a conversation
- Press "Start call"
- Immediately press back
Expected
If the join call request finishes, it should be left again afterwards
Actually
"Leave call" reaches the server before the join finishes.
This leads to wrong order of join/leave messages and results in "has_call" being left on for the conversation. Of course the API should make sure to clear up the state when a person leaves, but then again the requests should also be sent in the correct order (dont leave before join finished)
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 with the Android flow behind the “Start call”/join and “Leave call” actions, then reproduce the sequence on a slow connection. Trace the API request ordering when back is pressed immediately; done means the join completes before leave is sent and the conversation’s call state is cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100