Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotty push notifications delivery on iOS #1383

Closed
eoger opened this issue May 6, 2020 · 4 comments
Closed

Spotty push notifications delivery on iOS #1383

eoger opened this issue May 6, 2020 · 4 comments
Assignees
Labels

Comments

@eoger
Copy link

@eoger eoger commented May 6, 2020

I've noticed some Push notifications sent from the FxA servers never seem to arrive on iOS on a regular basis. We've investigated on the FxA side and it looks like Autopush is returning an error (we think a 502) calling the Push endpoint, but we didn't get more information.

From the slack conversion on #push, some errors were logged but couldn't get serialized to a string:
"message": "Uncaught exception in write_error: "

@jrconlin
Copy link
Member

@jrconlin jrconlin commented May 6, 2020

Will contact you offline, but I'm going to need a few things to diagnose what's going on here.

If possible, could you provide:
Sample message content for a notification.
if this is prod or stage
potentially some APNs credentials so I can test this outside of some sandbox type application, etc.

@eoger
Copy link
Author

@eoger eoger commented May 6, 2020

This is happening on prod. I've sent you my test app by email. Thanks for looking into this!

jrconlin added a commit that referenced this issue May 6, 2020
…messages

Includes better logging for uncaught APNs errors, since those were
getting dropped by cyclone.

Closes #1383
jrconlin added a commit that referenced this issue May 6, 2020
…messages

Includes better logging for uncaught APNs errors, since those were
getting dropped by cyclone.

Issue #1383
Closes #1384
@tublitzed tublitzed added this to Backlog: Misc in Services Engineering via automation May 7, 2020
@tublitzed tublitzed moved this from Backlog: Misc to Prioritized in Services Engineering May 7, 2020
@tublitzed tublitzed added the bug label May 7, 2020
pjenvey pushed a commit that referenced this issue May 7, 2020
…messages (#1385)

* bug: do not require `encryption` header for APNs `aes128gcm` encoded messages

Includes better logging for uncaught APNs errors, since those were
getting dropped by cyclone.

Issue #1383
Closes #1384
@tublitzed tublitzed moved this from Prioritized to Backlog: Push in Services Engineering May 11, 2020
@tublitzed tublitzed moved this from Backlog: Push to Prioritized in Services Engineering Jun 17, 2020
@tublitzed tublitzed moved this from Prioritized to In Review in Services Engineering Jul 13, 2020
@scheinercc
Copy link

@scheinercc scheinercc commented Jul 17, 2020

Could this be related? mozilla-mobile/fenix#8582

@jrconlin
Copy link
Member

@jrconlin jrconlin commented Jul 17, 2020

@scheinercc I don't believe so, since the bridge system for FCM is different than for iOS, we generally detect unregistered users better. Still #1415 may help address any similar problem if it's present.

@tublitzed tublitzed moved this from In Review to Archived in Services Engineering Jul 20, 2020
@tublitzed tublitzed closed this Jul 30, 2020
Services Engineering automation moved this from Archived to Done Jul 30, 2020
@tublitzed tublitzed moved this from Done to Archived in Services Engineering Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants