Page MenuHomePhabricator

Fix sound issue for peer-based notifications
ClosedPublic

Authored by marcin on Wed, Aug 21, 4:18 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Sep 13, 1:20 AM
Unknown Object (File)
Tue, Sep 10, 11:11 PM
Unknown Object (File)
Mon, Sep 9, 7:35 PM
Unknown Object (File)
Mon, Sep 9, 3:14 PM
Unknown Object (File)
Mon, Sep 9, 7:56 AM
Unknown Object (File)
Sun, Sep 8, 6:48 PM
Unknown Object (File)
Sat, Sep 7, 2:18 PM
Unknown Object (File)
Sat, Sep 7, 12:37 PM
Subscribers

Details

Summary

The context is here. In this differential we disable encryption of sound property for peer notifications.

Test Plan

Ensure that peer notifications make sound. Execute parent differential test plan and ensure that each delivered notification makes sound.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

  1. Are there any other APNs fields that we need to surface outside of the encrypted blob like this? For instance, how about priority?
  2. Do we have a similar problem with other encrypted notifs, such as the FCM ones we use for Android?
  1. Are there any other APNs fields that we need to surface outside of the encrypted blob like this? For instance, how about priority?

Sound was the only one. The priority field is not a part of notification but a part of headers of HTTP request to APNS which are never encrypted.

  1. Do we have a similar problem with other encrypted notifs, such as the FCM ones we use for Android?

No, we don't send notification sound on Android. It is set locally on when notifications channel is first created. See here. createChannel implementation is in native code here. It does not mention sound but according to documentation notifications sent to this channel will make sound since its importance is HIGH. The value of this sound is some default set by the system. User can change it in settings.

This revision is now accepted and ready to land.Mon, Aug 26, 5:19 AM