You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported in the Element X public room, it seems that if you create a DM with someone after having left a DM with them (we don't allow creating 2 DMs with the same user), the m.direct ends up with 2 entires for that user ID. There is then a second issue at play, where if there are 2 entries for the same user ID, the SDK doesn't recognise the new DM as a direct (I haven't dug into what gets decoded).
Reported steps to reproduce:
1. Both sides cleaned `m.direct`
2. A starts DM with B
3. Chat is shown as DM by EX of A and as Room in EX of B
4. B opens EW in Browser where it is shown as DM and clicks on DM with A
5. Chat is shown as DM in EX of B
6. A and B leave room
7. A starts DM with B
8. Chat is shown as DM by EX of A and as Room in EX of B
9. B opens EW in Browser where it is shown as DM and clicks on DM with A
10. Chat is NOT shown as DM in EX of B
I'm not sure what is going on with 4/5 but I think the important thing here is that by 10 you have two entires in the m.direct.
As reported in the Element X public room, it seems that if you create a DM with someone after having left a DM with them (we don't allow creating 2 DMs with the same user), the
m.direct
ends up with 2 entires for that user ID. There is then a second issue at play, where if there are 2 entries for the same user ID, the SDK doesn't recognise the new DM as adirect
(I haven't dug into what gets decoded).Reported steps to reproduce:
I'm not sure what is going on with
4
/5
but I think the important thing here is that by10
you have two entires in them.direct
.We're creating DMs with the following:
The text was updated successfully, but these errors were encountered: