-
message.id
is not specified to be unique and a long time ago it could even be not sent but it is recommended to be unique globally or at least within the current stream.Normally BeagleIM uses MAM to deduplicate incoming messages. However, your server does not support MAM and in this case, BeagleIM uses
message.id
for deduplication of incoming messages. Due to that those messages are not saved as we've not encountered any client which would send a non-randomized value as a messageid
attribute.We will look into this issue in the future version, but it is going to be a large version so this will not be a fast fix.
Describe the bug Hi. I found a bug that not all messages from conversation is displayed in chat window and does not appear in history. But when I open BeagleIM XML console I see that messages is coming to me.
To Reproduce Have no idea hot to reproduce, but I often see that bug.
I use BeagleIM 4.1 (110) on MacOS 11.1. Originally install BeagleIm from brew cask. When I recognise that bug I reinstall app from AppStore – but that is not fixed the bug.
I and my contact have accounts on jabber.ru server.
Desktop (please complete the following information):
At the and I attach the log from BeagleIM XML Console