(I am going to cross-post this in the Community too.)
OK, so according to the first example provided here, you can create a custom button to start a Web Messaging system and use the success / failure of the "Message.open" request to determine if there is a messaging session in place. If so, it should fail and that failure can be used to cause the chat to close.
I have a customer that is using this functionality, however it is no longer functioning. Code assigned to the Message Open and Message Close events works fine, and the "minimize" button at the top of the chat works as intended, so it looks to only be this part that is having issues.
It was first noticed this morning, but may have existed for a day or so. I assume that if it is down to an API change, it was part of this week's release?
Interesting, we noticed a subscribe event change that seems to have taken place about 2-3 days ago so I can't help but think this is more than coincidence.
Hi @PaulSimpson, we found this issue was introduced in the recent release and work is under progress to fix it. It should soon be out in a day or so and should continue to work as it was earlier on your end.
Do you have the details of this defect/issue and the fix? Is it possible that will also have addressed the messagingservice.ready problem that we're talking about in the other thread?
@VaunMcCarthy We recently made changes and improved Messenger to support rendering the Launcher button and Messenger UI in their own iframes rather than using one single iframe. This allows customers to interact with any buttons or UI elements under the Messenger (side by Launcher button). As a result of this bug with Messenger.open was introduced that is now fixed.
With MessagingService.ready, there are no changes. That works as expected. This is nothing to do with that.