Issues with disconnect after chatSession.endChat
Closed this issue · 2 comments
Having issues with the self-hosted widget from Amazon Connect.
After disconnect (chatSession.endChat) the new script behind scenes (amazon-connect-chat-interface.js) is making another API call which fails, getting 403 Access denied.
Using an old script (2-3 years old) after disconnect that API call to event isn't made.
Does anyone know why the new script is behaving like this?
Hi adelatanca99, the new behavior is because we added read/delivery receipts feature last year. This is a known bug that happens when a chat ends before the read/delivery events get a chance to fully propagate. We have a back log task to clean up this bug but it should not affect any chat functionality. Please reach out if you have any other questions.
Related issue amazon-connect/amazon-connect-chat-interface#168
Hi @adelatanca99,
Team has released ChatJS fix to address this issue. Please use latest version: npm install amazon-connect-chatjs@~2.2.2
I have generated a bundle file from ChatInterface/master if you need to use it:
https://github.com/amazon-connect/amazon-connect-chat-interface/blob/spenlep/bundle-file-latest-chatjs/amazon-connect-chat-interface.js
Resolving issue
-Spencer