You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug; what happened?
The interface CallAndChatLocator only supports GroupCallLocator type for the callLocator field
What are the steps to reproduce the issue?
Install npm package @azure/communication-react, version 1.22.0
What behavior did you expect?
I can set a RoomCallLocator in the callLocator field in interface CallAndChatLocator . The CallAdapterLocator used by the CallComposite does support this.
If applicable, provide screenshots:
In what environment did you see the issue?
@azure/communication-react npm package version 1.22.0
OS & Device: Win 11, PC
Browser: Any
Browser Version: Any
Is there any additional information?
The text was updated successfully, but these errors were encountered:
Hi @adrian-crisan625, Thanks for filing this issue. RoomCallLocator was not intended to be included in CallAndChatLocator because the rooms does not yet support chat threads. While technically it is possible to create a chat thread for a rooms call, there would be no access control done by the Rooms client as of today and any ACS user could join that chat thread.
Describe the bug; what happened?
The interface CallAndChatLocator only supports GroupCallLocator type for the callLocator field
What are the steps to reproduce the issue?
Install npm package @azure/communication-react, version 1.22.0
What behavior did you expect?
I can set a RoomCallLocator in the callLocator field in interface CallAndChatLocator . The CallAdapterLocator used by the CallComposite does support this.
If applicable, provide screenshots:
In what environment did you see the issue?
@azure/communication-react
npm package version 1.22.0Is there any additional information?
The text was updated successfully, but these errors were encountered: