Open maurice-baez opened 4 months ago
@xTEddie Would you be able to assist here?
@xTEddie adding some more context -
-adding .setDebug(true)
for more robust logging reveals something interesting -
The first image, shows browser logs up to the point where the chat errors out, the second image shows browsers logs indicating a successful session init/getChatToken, which occurs AFTER the chat has failed on the MessagingClientConversationJoinFailure
To me, it seems like it makes sense that it would not be able to create a conversation without a chat token/session, but why this timing issue is occurring is not clear. Like I mentioned earlier, I'm using essentially the exact same code as posted on the sandbox site, so why it would work there and not locally within my app doesn't make sense to me. Again, any help would be appreciated.
@maurice-baez Is it only happening locally? I've tried it via a localhost server, haven't tried it by deploying it. Any more insights into that?
@pavan-kumar-js - happening for me both locally and in a deployed environment.
@pavan-kumar-js - happening to me also using NODE JS
Hello -
I'm trying to connect to my chat widget via the Omnichannel SDK but running into an issue when starting the chat.
const chatSDK = new OmnichannelChatSDK(omnichannelConfig);
)initialize
(chatSDK.initialize()`)chatsSDK.startChat()
with the error:ChatSDKError {message: 'MessagingClientConversationJoinFailure', httpResponseStatusCode: undefined}
- the error happens here:Specs:
"@microsoft/omnichannel-chat-sdk": "^1.8.1-main.e44745c",
(also tried v1.5.5 (the same being used in the demo site)package.json
:Help would be greatly appreciated, please let me know if there's any other info needed. Thank you.