Skip to main content
Solved

Suddenly started getting error "Not delivered - connection issues"

  • January 27, 2025
  • 5 replies
  • 94 views

jamesai
Forum|alt.badge.img

 

I have integrated the Chat Widget code in my iOS app. It was working very good.

But today I noticed suddenly getting error in RED “Not delivered - connection issues” 

I have noticed the first message is delivered successfully but after that always getting the mentioned error.

When I tried to run the code in my browser it shows AxiosError. 

What could be the reason?

Here is my latest code

<html>
<body>
<script src="https://chat.frontapp.com/v1/chat.bundle.js"></script>
<script>
function initChat(name, userId, userHash) {
window.FrontChat('init', {
chatId: 'ce4c58cd0f7cbcd3ed3eaf3b0b0XXXX',
useDefaultLauncher: true,
shouldShowWindowOnLaunch: false,
shouldMobileReloadOnClose: true,
name: name,
userHash: userHash,
userId: userId,
onInitCompleted: () => {
logEvent("frontChatInitialized", { status: true });

window.FrontChat('onUnreadChange', (unreadCount) => {
logEvent("onUnreadChange", unreadCount);
});

window.FrontChat('onWindowVisibilityChanged', (visibility) => {
logEvent("onWindowVisibilityChanged", visibility);
});

// Set interval to continuously check if the element is loaded
var intervalId = setInterval(removeWidgetRoundedCorners, 1000);
},
});
}

initChat(
'Jen Lee at lblinth231',
'Dear_2777628Jen_Lee',
'f7b35fe9d28d63ec2d8066835c00d732d1f7246e520bb292aff12c72ad3f47b2'
);

setTimeout(() => {
window.FrontChat('show');
console.log("DELAY 2");
}, 2000);

function logEvent(event, jsonData) {
const formattedEvent = {
event: event,
data: jsonData,
};
console.log(JSON.stringify(formattedEvent));
}

function showChat() {
console.log("show chat called");
window.FrontChat('show');
}

function clearSession(name, userId, userHash) {
logEvent("clearSessionCalled", { name, userId, userHash });
window.FrontChat('shutdown', { clearSession: true });
}

</script>
</body>
</html>

 

Best answer by raymond_ching

Hi James, thanks for the screenshot! We will reach out to assist since this might be specific to you.

5 replies

jamesai
Forum|alt.badge.img
  • Author
  • Conversationalist
  • January 28, 2025

This is the responseText I am getting 

  1. "{\"name\":\"FrontError\",\"status\":\"forbidden\",\"reason\":\"User Dear_2777628Jen_Lee cannot access the specified conversation 2f519654-75d0-4c31-9011-ba320cfbaaf9\",\"message\":\"User Dear_2777628Jen_Lee cannot access the specified conversation 2f519654-75d0-4c31-9011-ba320cfbaaf9\"}"

 

I am not sure, is there any problem with the code? why the same user has the access to the specified conversation on first message and it is delivered correctly?


Forum|alt.badge.img+5

Hi James,

Sorry to hear about your issues with Front chat - I believe we had a small incident yesterday that may have impacted sending on Front chat. Do you still experience this issue today? If so, can you please write in to us at support@frontapp.com with a specific chat conversation example? We can take a deeper look from there, thank you!


jamesai
Forum|alt.badge.img
  • Author
  • Conversationalist
  • January 29, 2025

Hi James,

Sorry to hear about your issues with Front chat - I believe we had a small incident yesterday that may have impacted sending on Front chat. Do you still experience this issue today? If so, can you please write in to us at support@frontapp.com with a specific chat conversation example? We can take a deeper look from there, thank you!

Thank you for the response ​@raymond_ching. I thought so its from front side problem.

Well I have changed my code a bit now. previously I was login into front chat with userId (that had the above mentioned problem), But now I am login into front chat via email which works fine i.e no more “Not delivered - connection issues” error


jamesai
Forum|alt.badge.img
  • Author
  • Conversationalist
  • January 29, 2025

I just confirmed again. problem is still there with the userId

 


Forum|alt.badge.img+5
  • Fronteer
  • Answer
  • January 29, 2025

Hi James, thanks for the screenshot! We will reach out to assist since this might be specific to you.