The message sent by the server contains the special character "&". Now after starting the program, it will continue: authentication succeeded -> receiving message -> lost link -> reconnect -> authentication succeeded ->...
I think it is because, first, the xmpp login is successful, and the server sends an offline message. After the app receives the message, the parsing fails, and the receipt message is not sent to the server. As a result, the server sends this message every time after the xmpp authentication succeeds. . This is an endless loop.
The above are my thoughts.
Is there any way to handle it on the app side? Or do I need to handle it on the server side?
The message sent by the server contains the special character "&". Now after starting the program, it will continue: authentication succeeded -> receiving message -> lost link -> reconnect -> authentication succeeded ->... I think it is because, first, the xmpp login is successful, and the server sends an offline message. After the app receives the message, the parsing fails, and the receipt message is not sent to the server. As a result, the server sends this message every time after the xmpp authentication succeeds. . This is an endless loop. The above are my thoughts. Is there any way to handle it on the app side? Or do I need to handle it on the server side?