search

queelag / fcm

MIT License
6 stars 2 forks source link

FcmClient -> onSocketDataBytes -> Failed to read current message, resetting size packets and waiting for more bytes. #13

Open dhirajtechnostacks opened 1 month ago

dhirajtechnostacks commented 1 month ago

Getting this error.

FcmClient -> onSocketDataBytes -> Failed to read current message, resetting size packets and waiting for more bytes. FcmClient -> onSocketDataSizeTimeout -> The size state has timed out, ready for the next message.

kcespedes commented 1 month ago

Hi, im getting the same error, have you found a solution or work around for it?

sallar commented 2 weeks ago

Im having the same issue, and this only happens when there are too many notifications on FCM server waiting to be retrieved

sallar commented 2 weeks ago

After several disconnects and connects, the queue finally clears up and I start receiving notifications again, and no more timeouts.

haomingli2020 commented 1 week ago

Hi all, I'm also getting this issue on every push notifications (including the first one received on a fresh FCM token). Is it relevant to the incoming data size? Heartbeat and login messages are showing fine because they are less than 20 bytes but when I printed the size of a notification message, it was over 600 bytes and triggering these errors. I've checked the resolved issues and followed all the solutions, such as adding ece in the input when calling new FcmClient() . Still I'm getting the same errors.