Closed kevincox closed 4 months ago
That's a client bug, it means the client used a megolm session that's too old (by default the expiry is 1 week and the bridge deletes sessions that are >2x the expiry, so the session was at least 2 weeks old)
Yes, it seems that you are right. I tried after restart with a different client. Trying again with the original client (Element Android) still fails. The bridge was set up just over 2 weeks ago so I guess keys were never refreshed.
For anyone suffering the same issue: AFAIK it only affects Element Android, and refreshing session by sending /discardsession
in the room seems to mitigate it.
When trying to send messages the bot was responding with:
I tried a few times with the same problem. After restarting the bridge everything seemed back to normal.
Logs
There weren't really any logs. Just the one error that was also presented in the response from the bot. I've included a few previous log messages but they are quite a bit before I sent the message that failed to get bridged.
Version: https://github.com/mautrix/meta/commit/61f9c3985d2025d3dd89a8ee4a8a9e95e2961c81