diff options
| author | 2023-02-15 13:49:48 -0500 | |
|---|---|---|
| committer | 2023-02-15 17:04:56 -0500 | |
| commit | bd4708cd6cf16435b026e24d5123c8f2c28c2ea6 (patch) | |
| tree | 36c389853f309972b460cd53f09041f3649804a9 /api/api_test.go | |
| parent | 0d74676c7bc84d1a18213cec7268cd0085755ae2 (diff) | |
Track whether we've logged the "intercepted" state of a record.
We didn't have any direct way to determine whether we'd already logged something intercepting (we guessed using the "intercepted" value and whether the record was an update), so we were sometimes double-logging the interception statement.
Further, add additional logging for when the intercepted status is changed for a record. This may happen in the case of re-considering whether a notification should alert after a contacts lookup comes back when DND is on.
Bug: 264918364
Test: manual by confirming zen log after sending a notification updated to break through DND and alert, and various types of notifications that did and did not break through (messages, calls, priority apps)
Test: NotificationManagerServiceTest, ZenModeFilteringTest
Change-Id: Iac37f6af171b05fa3eac61e16be99ae5f36c0b12
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions