While being in a call, I dont receive messages sent during the call
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- 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
- Have a call with someone
- Tell that someone to send messages to your 1:1 chat
- No messages received
Expected behaviour
I should see/read the messages
Actual behaviour
On the left sidebar i see that i have unread msg. But no messages are shown on the chat
Talk app
Talk app version: (see apps administration page: /index.php/settings/apps)
Custom Signaling server configured: yes/no and version (see Talk administration settings: /index.php/settings/admin/talk#signaling_server)
Custom TURN server configured: yes/no (see Talk administration settings: /index.php/settings/admin/talk#turn_server)
Custom STUN server configured: yes/no (see Talk administration settings: /index.php/settings/admin/talk#stun_server)
Browser
Microphone available: yes/no
Camera available: yes/no
Operating system: Windows/Ubuntu/Mac/...
Browser name: Firefox/Chrome/Safari/...
Browser version: 124/125/...
Browser log
Server configuration
Operating system: Ubuntu/RedHat/...
Web server: Apache/Nginx
Database: MySQL/Maria/SQLite/PostgreSQL
PHP version: 8.1/8.2/8.3
Nextcloud Version: (see administration page)
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Server log (data/nextcloud.log)
Insert your server log here
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
No source file, test, or entry point is identified. Start by reproducing the issue during a 1:1 call and collect the missing Talk, browser, server, and configuration details; done means messages sent during the call are visible in the chat.
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
- 30/100