nextcloud / nextcloud/spreed

Signaling error does not disappear in some case, although joined

Open
#11,216 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: frontend 🖌️ feature: signaling 📶
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Something happens that triggers a signaling error
  2. Join a conversation
Expected behaviour

At least after successful joining the error should disappear

Actual behaviour
image

I can see
image

but not sure if this related.

Talk app

Talk app version: 18 on c.nc.c

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

Reproduce the issue using the two listed steps: trigger a signaling error, then join a conversation. No source file, test, or specific entry point is named, so trace the signaling and successful-join flow first; done means the error no longer remains after joining.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.