You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a reported case of a group message not set to "sent" status in the database, despite the SM ack was correctly received by the server. Check the whole message confirmation workflow.
What apparently happened:
message was sent from resending queue after connection was authenticated (log present: "resending message...")
ack came through but the message was not set to "sent"
a couple of minutes later network changes and connection is restarted
message is sent again right after authentication (no log this time. What?!?) and confirmed, but status was not sent (still pending)
message is sent once again after the multicast service replies with discovery information (this time it's the correct workflow, with "resending message" log line)
message was confirmed by server but still not set to "sent" status
at the next reconnection, the message is correctly sent again, this time the status was set to "sent"
Ack handled message count by the server was always correct, so I'm assuming the problem is client-side.
The text was updated successfully, but these errors were encountered:
I had a reported case of a group message not set to "sent" status in the database, despite the SM ack was correctly received by the server. Check the whole message confirmation workflow.
What apparently happened:
Ack handled message count by the server was always correct, so I'm assuming the problem is client-side.
The text was updated successfully, but these errors were encountered: