Client is not properly backfilling room history with federation #4374
Labels
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
We’re using Synapse/1.105.1 on the server side and matrix-js-sdk in our react native app. We have two servers, server A and server B. The room is created on server A, and users are invited, one from server A and one from server B. The user A joins the room and sends the message. Afterwards, the user B joins, but the message or anything else from before the /join is not federated, the room is there, everything seems okay, but the history is missing. Only after we send something else from server A, for example another message, this triggers or rather pulls the federation of the history as well. History visibility is set to shared, everything works as intended afterwards.
Calling API manually (from Postman or calling the api directly outside of the client for example) triggers the federation properly: calling /sync and afterwards /messages works as intended, so this is most likely not a Synapse issue. However, we cannot make the client backfill the history.
Steps we do:
We also tried paginating backwards, we get state events prior to the first message, but not the message itself.
Is there a solution for this, can we somehow make sure that the history is available when the user joins the room? I found similar issues but nothing exactly the same nor the explanation how to force syncing the room.
The text was updated successfully, but these errors were encountered: