Spotty push notifications delivery on iOS #1383
Closed
Comments
|
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: |
|
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
|
Could this be related? mozilla-mobile/fenix#8582 |
|
@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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: "The text was updated successfully, but these errors were encountered: