[Problem/Question]
When freezing an Open Channel using the Sendbird Platform API, the onChannelFrozen event is not triggered on client applications. However, when freezing the same channel via the Sendbird Dashboard (by clicking the Freeze icon in the Moderator section), the event is successfully received by clients.
[SDK Version]
Client: @sendbird/chat": "^4.16.4
Server: Java 17 with Spring Boot 3.1.3
[Reproduction Steps]
Clients register an OpenChannelHandler and enter the Open Channel.
The server sends a PUT request to freeze the channel:
PUT https://api-{application_id}.sendbird.com/v3/open_channels/{channel_url}/freeze
Content-Type: application/json
Api-Token: {api_token}
{
“freeze”: true
}
Clients do not receive the onChannelFrozen event.
When freezing the same channel via the Sendbird Dashboard (Chat > Open Channels > [Channel] > Freeze icon), clients receive the onChannelFrozen event as expected.
[Frequency]
This issue occurs consistently whenever the channel is frozen via the Platform API.
Sendbird
[Current Impact]
Clients are unaware that the channel has been frozen, leading to a lack of appropriate UI updates or user notifications.
[Additional Information]
Clients are connected, have entered the channel, and have registered the OpenChannelHandler.
The discrepancy suggests a potential difference in event propagation between the Dashboard and API methods.
According to the Sendbird documentation, the onChannelFrozen event should be triggered on all devices where client apps with the channel are in the foreground, including the device where the channel was frozen.
Sendbird
