nextcloud / nextcloud/talk-android

No automatic reconnect on instable connection

Open
#2,368 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

Steps to reproduce
  1. Connect to call in wifi
  2. partner uses windows (Chrom 05.0.5195.102) from extern
  3. Talk with partner
  4. After time disconnects
  5. No reconnect. It looks like partner on the android device left the call even though he / she didn't.
Expected behaviour

If the connection is instable the app will try to reconnect in a loop or so and not leave the call just like that.
For the server it looks leaving the call. thats why there is no serverside errors.

Actual behaviour

No reconnect on lost connection between partner within different networks.
The only way is to reload the chats and rejoin.

Device brand and model

Samsung Note10+

Android version

12

Nextcloud Talk app version

14.2.0

Nextcloud server version

24.0.5

Talk version

14.0.4

Custom Signaling server configured

Yes (specify version in Additional Information)

Custom TURN server configured

Yes

Custom STUN server configured

Yes

Android logs

where are the logs of the talk app, how to enable debug mode?
I see no logs there...

Server log
no errors as it looks like a leaving of the call
Additional information

nextcloud signaling server : https://github.com/strukturag/nextcloud-spreed-signaling (latest version installed with docker)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by running the listed Wi-Fi and external-partner reproduction steps on the specified Android setup, then trace the call behavior when the connection drops. Done means the app retries the connection without leaving the call and the scenario no longer requires reloading chats and rejoining.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
audio-video-rtc, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.