-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat messages suddenly limited to 6 per thread in ChatComposite #4625
Comments
Thanks for logging this issue. Will share with the team and get back to you on a response. |
Hi @olandahl, |
When I did some debugging in dev tools I found updates to the messages state that where the number of items were limited to 6. I assumed the data came from web socket. I can't find that place in the code now but I'll let you know if I do. Hopefully I'll have time to create a sample app where the issue is reproducable. The issue is also in Safari. The rendered ChatComposite on the dev site, including all messages: The rendered ChatComposite on localhost, including 6 messages: The request to https://acs-onewound-dev.europe.communication.azure.com/chat/threads/19%3AXj9G4INqH_jHAGuOLVAWVqrFF0okXxSuAEUakQRgAEQ1%40thread.v2/messages?maxPageSize=50&api-version=2024-03-01-preview (made by the ChatComposite component) is identical in localhost and on the dev site. It includes all messages. |
Hi @olandahl, |
Close the issue right now since long time no response. Please be free to re-open the issue if you have more questions |
I'm using the ChatComposite component to display a chat thread. A backend create threads, add users and some custom messages. Everything is working fine, it's possible to add messages, edit, remove, and so on. Suddenly all threads show only the 6 latest messages, even when the page is reloaded. I can see all messages are included in the REST API /messages response (done by the ChatComposite component) but it seems the WebSocket data is limited to 6 messages.
This happens when running on localhost. In a public dev environment (using the same ACS instance) all messages are still displayed.
Is there some kind of rate limit that kicks in? We're not even close to hit the service limits for the chat (https://learn.microsoft.com/en-us/azure/communication-services/concepts/service-limits#chat)
We use beta versions to get some features that are missing in the latest offical releases:
"@azure/communication-chat": "^1.5.0-beta.1",
"@azure/communication-react": "^1.15.0-beta.2",
Running in Chrome v 124
The text was updated successfully, but these errors were encountered: