fixed behaviour in message parser when doing mam catchup

Daniel Gultsch created 9 years ago

Change summary

src/main/java/eu/siacs/conversations/parser/MessageParser.java | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Detailed changes

src/main/java/eu/siacs/conversations/parser/MessageParser.java

@@ -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);
 				}
 			}