This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Enforce senderID requirement for GCM/FCM records #868
Assignees
Comments
jrconlin
added a commit
that referenced
this issue
Apr 13, 2017
jrconlin
added a commit
that referenced
this issue
Apr 13, 2017
jrconlin
added a commit
that referenced
this issue
Apr 13, 2017
jrconlin
added a commit
that referenced
this issue
Apr 13, 2017
jrconlin
added a commit
that referenced
this issue
Apr 13, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've seen a few reports of *cm records that do not include a
senderIDin their router data.https://sentry.prod.mozaws.net/operations/autopush-prod/issues/358097/events/9996820/
We should consider those records to be a critical failure and mark them appropriately.
NOTE: This may disable notifications to this client, but they weren't getting through anyway.
The text was updated successfully, but these errors were encountered: