fixed behaviour in message parser when doing mam catchup
This commit is contained in:
parent
bb249e0881
commit
c7e95d105c
|
@ -539,7 +539,7 @@ public class MessageParser extends AbstractParser implements OnMessagePacketRece
|
|||
query.incrementActualMessageCount();
|
||||
}
|
||||
|
||||
if (query == null || !query.isCatchup()) { //either no mam or catchup
|
||||
if (query == null || query.isCatchup()) { //either no mam or catchup
|
||||
if (status == Message.STATUS_SEND || status == Message.STATUS_SEND_RECEIVED) {
|
||||
mXmppConnectionService.markRead(conversation);
|
||||
if (query == null) {
|
||||
|
@ -581,7 +581,7 @@ public class MessageParser extends AbstractParser implements OnMessagePacketRece
|
|||
} else if (notify) {
|
||||
if (query == null) {
|
||||
mXmppConnectionService.getNotificationService().push(message);
|
||||
} else if (query.getWith() == null) { // mam catchup
|
||||
} else if (query.isCatchup()) { // mam catchup
|
||||
mXmppConnectionService.getNotificationService().pushFromBacklog(message);
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue