Hi,

If you use the terminate or endChat:false, the SDK will close the socket, not terminate the whole conversation. The conversation still can be continued until the session token is not expired.

Hi ios_dev,

It was a merge mistake, I apologise for this. We corrected the sample application code, now it should update to the latest official release, 1.10.2.

I also notice the project has been updated to use 1.11 but I do not see a 1.11 release in the podspec repo? so the pod update and project build now fails...

hey @Eliza_Koren perhaps @Andras_Solyom any idea why we do not see an end to the chat from the agent point of view when these functions are called?

ah thanks for that. One more observation. the functions in the sample app for ending a chat on the mobile app:

/**
 Ends current chat handler.
 */
- (void)endChat:(BOOL)forceClose;

/**
 Teminates the chat controller and all active chats.
 */
- (void)terminate;

These are not informing the Agent that the user has left the chat. is this a bug?

Thanks

Hi Chris,

Thank you for sharing the details of the issue.

There are two specific flows you’re looking for:

1. Triggering the didReceiveChatElement event when a chat element is received from the agent.
2. Receiving a notification when the agent sends messages to the user, even when the user is navigating outside the chat window.

Feedback:

• Passing events for received messages should indeed be possible via didReceiveChatElement. - We were able to reproduce the issue and bug was opened and will be fixed on version v1.11.1.
• Currently, we do not support sending notifications to users while the chat window is inactive. This functionality will be available once Push Notifications are implemented. - Push Notification feature is in our roadmap for 2025.

BR,
Eliza