Socket management for in app notifications

Hello, I am using the in-app notification to send a real-time notification to a player when another player attacked him (kind of passive multiplayer). We also use this notification to update the attacked (notified) player stats in real-time. For some reason that I didn’t manage to identify or reproduce yet, it sometimes happens that a player does not receive the notification. this of course then leads to other problems as the player’s local stats are not compatible with the stats on the server. I am suspecting it has something to do with the socket I am opening at the beginning of the sessions and use it to listen to the in-app notification, are you familiar with any similar problem, are there any rules or practices that need to be made make sure the socket is always alive? (Today I am simply creating the socket at the beginning of the session)

Thanks

@oshribin I think you were able to make progress on this for your game. Do you have code or advice you can share on what approach you used? Are you still stuck on any parts?