For more details on this issue, please see the matrix-js-sdk v19.7.0 release announcement. Redacting a specific type of event or clearing its storage can resolve this issue. Redacting all events of a specific type or clearing all storage will fix the issue further. Redacting applied events and clearing all storage will fix the issue further. If a consumer is experiencing beacons that are either not being sent or are being sent in an unredacted way, this issue can be resolved by redacting all applicable events. As an additional option, storage can be cleared and re-initiated.
How do I fix this issue?
For more details on this issue, please see the matrix-js-sdk v19.7.0 release announcement. Redacting a specific type of event or clearing its storage can resolve this issue. Redacting all events of a specific type or clearing all storage will fix the issue further. Redacting applied events and clearing all storage will fix the issue further. If a consumer is experiencing beacons that are either not being sent or are being sent in an unredacted way, this issue can be resolved by redacting all applicable events. As an additional option, storage can be cleared and re-initiated.
Beacons that are not being sent
If beacons are not being sent, please redact all applicable events and clear all storage.
Summary
For more details on this issue, please see the matrix-js-sdk v19.7.0 release announcement. Redacting a specific type of event or clearing its storage can resolve this issue. Redacting all events of a specific type or clearing all storage will fix the issue further. Redacting applied events and clearing all storage will fix the issue further. If a consumer is experiencing beacons that are either not being sent or are being sent in an unredacted way, this issue can be resolved by redacting all applicable events. As an additional option, storage can be cleared and re-initiated.
Fixed: Beacons that are not being sent after an update to matrix-js-sdk
If you are experiencing beacons not being sent after an update to matrix-js-sdk, please be sure that the updated version of matrix-js-sdk is running and that events are redacted. If you are also experiencing redacting not working at all, this issue can be resolved by clearing all applicable event storage. Redacting applicable events will fix this issue further.
How Can I Find Out If My Organization Is Affected By This?
If you are experiencing this issue, please read the matrix-js-sdk v19.7.0 release announcement for more information on how to resolve it.
Timeline
Published on: 09/28/2022 17:15:00 UTC
Last modified on: 10/31/2022 22:15:00 UTC
References
- https://github.com/matrix-org/matrix-js-sdk/commit/a587d7c36026fe1fcf93dfff63588abee359be76
- https://github.com/matrix-org/matrix-js-sdk/releases/tag/v19.7.0
- https://github.com/matrix-org/matrix-spec-proposals/pull/3488
- https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-hvv8-5v86-r45x
- https://security.gentoo.org/glsa/202210-35
- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39236