Skip to content

Tolerate invalid account data events

Olivia Lee requested to merge benjamin/handle-bad-account-data into main

Validated that this fixes #46 (closed) by pointing element at a test instance. I was able to reproduce all three versions of the bug on main, and confirmed that all three are fixed on the branch. The three variants are:

  • users with m.direct account data that doesn't match the schema from the spec are unable to join upgraded rooms
  • if a user with m.direct account data that doesn't match the schema from the spec attempts to upgrade a room, both the original and new rooms are bricked
  • if you set m.direct account data with extra fields not present in the spec, they are erased when joining an upgraded room

Merge request reports