This differential fixes urget issue:
https://linear.app/comm/issue/ENG-6010/invariant-violation-collapsible-notifications-encryption-currently-not.
We want to keep the invariant active since it protects us against accidentally exposing unencrypted
collapseID in notification headers. We just need to put it in notification payload for MacOS notifs as well.
Putting collapseID in notification.collapseID results in collapseID being exposed in notification
headers. Putting it in notification.payload results in collapseID being encrypted.
Details
Details
- Build MacOS desktop app.
- Send collapsible notifications (chenge the color of the thread for instance).
- Ensure that notifications are displayed correctly and version field in MariaDB of relevant olm session
is incremented with each notification.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
keyserver/src/push/send.js | ||
---|---|---|
970 ↗ | (On Diff #34262) | This is a weird condition to see. Why are the conditions for iOS and macOS named differently? Can we rename them to be more similar? And maybe canDecryptIOSNotifs can be more like iosCanOnlyDecryptNonCollapsibleNotifs or something? |
Comment Actions
Enhance variable naming in contitions that determine whether notifications should be encrypted