Can´t add Federated Users to group chats.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 586
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
[!TIP]
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
- Add a Federated Server as trusted server
- Create a group chat, try to add an user via their federated cloud ID
Expected behaviour
User should be added to group chat.
Actual behaviour
User isn´t added, but error "An error occurred while adding participants" displayed.
Federated sharing with the user via NC files works as intended.
Talk app
Talk app version: 22.0.17 on both sides
Custom Signaling server configured: no
Custom TURN server configured: no
Custom STUN server configured: no
Browser
Browser name: Chrome
Browser version: 151.0.7922.170
Server configuration
Nextcloud Version: 32.0.14.1 on our NC, 31.0.14.1 on Federated NC
Server log (data/nextcloud.log)
"message": "Failed to create federation provider",
"userAgent": "Nextcloud Server Crawler",
"version": "32.0.14.1",
"exception": {
"Exception": "OCP\\Federation\\Exceptions\\ProviderDoesNotExistsException",
"Message": "Cloud Federation Provider with ID: \"talk-room\" does not exist.",```
</details>
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
Reproduce the group-chat invitation flow using the listed Nextcloud and Talk versions, then start with the server log entry for the missing "talk-room" federation provider. Trace the federated participant-addition path until the provider failure is located; done means a federated user can be added to a group chat without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100