Socket Error

[emmanuel-omegaalexis]

The username and password are correct but I keep getting a websocket error.
WebSocket connection to 'wss://api.chatengine.io/person_v4/?session_token=' failed:

[kuldeepperumalla]

same error! did you found any fix?

[emmanuel-omegaalexis]

I had to delete some of my Chats to get to work again (I had over 50). Maybe there is a limit or it was a fluke.

[HaAymar]

Is there any one who found the solution of how to solve the problem with the socket error pleasee !!
I can send message but , it can't show me the message I sent and also the response, but in the side of admin I can see all messages

Thank you

[HridoyHazard]

facing the same error

[HridoyHazard]

@kuladeepperumalla @emmanuel-omegaalexis @HaAymar @alamorre

[emmanuel-omegaalexis]

@HridoyHazard I deleted the chats and created new ones, I have not seen the error since. I thought was because I had too many chats (each user has over 200 chats each) but I have not been able to confirm that.

[HridoyHazard]

i tried this but still not working...getting the same error. but message is sending to the user but it needs to reload to see it from user end @emmanuel-omegaalexis

[AdiNehama]

did you solve it already? @HridoyHazard

[AdiNehama]

@alamorre

[adityaChauhan2510]

how to solve this error

[ClearConnect]

Hi @alamorre having similar problem with one important difference: While ChatFeed is working with the support example ( though I had to increase the timeout to 4000 to get it to work
, I get Socket Closed in our app ( I'm working for a healthcare startup)

Any suggestions will be much appreciated!

[ClearConnect]

By ellimination I figured out the websock problem was caused by </React.StrictMode> as soon as I removed it the problem went away. Chat GPT suggests Best Practices
Here are some best practices to handle such issues without removing <React.StrictMode>:

Idempotent Side Effects: Ensure that side effects (like WebSocket connections) are idempotent, meaning that initializing or cleaning them up multiple times has no adverse effects.
Check for Duplicates: Before creating a new WebSocket connection, check if one already exists and is in the correct state.
Proper Cleanup: Make sure that side effects are properly cleaned up in useEffect cleanup functions.
Does this make sense @alamorre ?

In case you guys are still struggling with this @kuldeepperumalla @emmanuel-omegaalexis @HaAymar @adityaChauhan2510 @adityaChauhan2510 @emmanuel-omegaalexis