nextcloud / nextcloud/talk-android

Call connection fails. ("code":"no_such_room","message":"The user is not invited to this room.")

Open
#3,863 0 comments 2 reactions 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

accept incoming call

Expected behaviour

call is established

Actual behaviour

Sometimes, call is not established. android logs:

2024-04-19 11:01:10.687 20031-20031 CallActivity            com.nextcloud.talk2                  D  fetchSignalingSettings
2024-04-19 11:01:10.987 20031-20031 CallActivity            com.nextcloud.talk2                  D     hasExternalSignalingServer: true
2024-04-19 11:01:10.987 20031-20031 CallActivity            com.nextcloud.talk2                  D  Update externalSignalingServer for: 2 / ....@......de
2024-04-19 11:01:10.987 20031-20031 CallActivity            com.nextcloud.talk2                  D     STUN server url: ..............com:443
2024-04-19 11:01:10.988 20031-20031 CallActivity            com.nextcloud.talk2                  D     TURN server url: ........com:443?transport=udp
2024-04-19 11:01:10.988 20031-20031 CallActivity            com.nextcloud.talk2                  D     TURN server url: ..........:443?transport=udp
2024-04-19 11:01:11.285 20031-20031 WebSocketC...tionHelper com.nextcloud.talk2                  D  Existing webSocketInstance found for user ..... (userId:2)
2024-04-19 11:01:11.286 20031-20031 CallActivity            com.nextcloud.talk2                  D  joinRoomAndCall
2024-04-19 11:01:11.286 20031-20031 CallActivity            com.nextcloud.talk2                  D     baseUrl= https://............com
2024-04-19 11:01:11.286 20031-20031 CallActivity            com.nextcloud.talk2                  D     roomToken= 9417879654
2024-04-19 11:01:11.286 20031-20031 CallActivity            com.nextcloud.talk2                  D     callSession= aF84v9Kb8zSrwD7IZnZpqjx9UdBPD5/FAYllrgAChPKSV4SOmYegh+GncQU4WX1cQ9u5Ug426BzSLlDS6vCrK0HsZVaZPlQdked/HAFyyvZDmBSYl+N6VGHkjV9S09WepUvBeXlzb/wpsL/Jf3ocKyuZS6YRplkgQkxHRmYlDeWa8sJOdm8+YqpqXMnlS0tzGpd+7PEE++qrEyB85fN7PeyNK0Q4hWMN4ywuyqMrjqhVl7HAHSDyUUbt1nyAF0P
2024-04-19 11:01:11.286 20031-20031 CallActivity            com.nextcloud.talk2                  D     url= https://.........com/ocs/v2.php/apps/spreed/api/v4/room/9417879654/participants/active
2024-04-19 11:01:11.286 20031-20031 WebSocketInstance       com.nextcloud.talk2                  D  joinRoomWithRoomTokenAndSession
2024-04-19 11:01:11.286 20031-20031 WebSocketInstance       com.nextcloud.talk2                  D     roomToken: 9417879654
2024-04-19 11:01:11.286 20031-20031 WebSocketInstance       com.nextcloud.talk2                  D     session: aF84v9Kb8zSrwD7IZnZpqjx9UdBPD5/FAYllrgAChPKSV4SOmYegh+GncQU4WX1cQ9u5Ug426BzSLlDS6vCrK0HsZVaZPlQdked/HAFyyvZDmBSYl+N6VGHkjV9S09WepUvBeXlzb/wpsL/Jf3ocKyuZS6YRplkgQkxHRmYlDeWa8sJOdm8+YqpqXMnlS0tzGpd+7PEE++qrEyB85fN7PeyNK0Q4hWMN4ywuyqMrjqhVl7HAHSDyUUbt1nyAF0P
2024-04-19 11:01:11.286 20031-20031 WebSocketInstance       com.nextcloud.talk2                  D  Sending join room message via websocket
2024-04-19 11:01:11.419 20031-26015 WebSocketInstance       com.nextcloud.talk2                  D  Receiving : okhttp3.internal.ws.RealWebSocket@86eed3a {"type":"error","error":{"code":"no_such_room","message":"The user is not invited to this room."}}
2024-04-19 11:01:11.419 20031-26015 WebSocketInstance       com.nextcloud.talk2                  E  Received error: {"type":"error","error":{"code":"no_such_room","message":"The user is not invited to this room."}}
Nextcloud Talk app version

18.0.0 & 19.0.0RC4

Nextcloud server version

29.0.0 RC5 & 30.0.0 dev

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

Start with CallActivity's joinRoomAndCall flow and WebSocketInstance.joinRoomWithRoomTokenAndSession, using the reported websocket log as the reproduction signal. Reproduce an accepted incoming call and inspect the room token, session, and invitation state around the join request. Done means the call is established without the no_such_room error.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.