Page MenuHomePhabricator

Add keyserverID to unencrypted notification and display to staff info about notification failure
ClosedPublic

Authored by marcin on Jul 17 2024, 8:07 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 25, 11:08 AM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 25 2024, 7:54 PM
Unknown Object (File)
Sep 18 2024, 7:09 PM
Subscribers

Details

Summary

This differential:

  1. Fixes recently introduced issue - notification was missing keyserverID after encryption failure.
  2. Unifies encryption failure indicator field - keyserver used to put encryptionFailed while the NSE checked for encryptionFailure
  3. Display additional error message notification to staff members if encryptionFailed key is present.
Test Plan
  1. Add throw in src/push/crypto.js.
  2. Send notification to iOS device.
  3. Ensure that two notifications are present: one correct and the other with encryption failure error message.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Mirror behaviour on Android

ashoat published this revision for review.Jul 17 2024, 8:59 AM

Can we continue printing the log when this happens, even for non-staff builds?

web/cpp/SQLiteQueryExecutorBindings.cpp
315 ↗(On Diff #42389)

Oops, not sure how I landed this with a Prettier issue. Thanks for the fix

This revision is now accepted and ready to land.Jul 17 2024, 8:59 AM

Log information about notification encryption failure regardless of user staff member status.