Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sent message not synced (MAM sync problem?) on other device #1574

Open
LionelHoudelier opened this issue Apr 20, 2024 · 3 comments
Open

Sent message not synced (MAM sync problem?) on other device #1574

LionelHoudelier opened this issue Apr 20, 2024 · 3 comments

Comments

@LionelHoudelier
Copy link

LionelHoudelier commented Apr 20, 2024

On device A (Android+Conversations) with account Z, I have sent a message with mp4 (10MiB) to a contact C
On device B with same Z account (Debian arm 3 GB RAM + dino-im), does not show the sent message from A.

Tried:

  • restart dino-im, restart device, many times
  • dino --print-xmpp=[to=contact] does not show anything when disconnecting/connecting the account.
  • the same message was sent to other contacts C1,C2,etc from A . It appears correctly on B, as sent, with success.

How could i get the missing sent message on dino-im????

@licaon-kter
Copy link
Contributor

Use a client that can setup your account MAM, say Conversations or Gajim, set it to Always.

Also, your server has Carbons?

Eg. https://compliance.conversations.im testing says 100% or close?

@LionelHoudelier
Copy link
Author

LionelHoudelier commented Apr 20, 2024

Use a client that can setup your account MAM, say Conversations or Gajim, set it to Always.

Already done. On device B2 and B3 (Android with Conversations) the client (Conversations) shows the sent message.
Same with B4 (Debian amd64 ) : Dino shows the sent message correctly.
Only on B, message does not get downloaded.

Also, your server has Carbons?

Yes

Eg. https://compliance.conversations.im testing says 100% or close?

Already tested.

It looks like Dino on B has missed to sync the message sent from A and cannot detect that it is missing it. Unfortunatly i cannot trace the problem or reproduce it because it works with the next messages with the same procedure. Any Idea to trace it?

@licaon-kter
Copy link
Contributor

See Wiki Debug, run with -print-xmpp=all and try to reproduce

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants