You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our case the client keeps receiving responses with code 401. The FCM authentication works fine, but the configured APNS key doesn't seem to be working temporarily, so the FCM servers aren't able to properly authenticate with Apple and just bubble the 401 back to the client. The response includes that information, but since it also happens to be a 401 it just keeps trying to refresh its access token until it times out.
{"error"=>
{"code"=>401,
"message"=>"Auth error from APNS or Web Push Service",
"status"=>"UNAUTHENTICATED",
"details"=>
[{"@type"=>"type.googleapis.com/google.firebase.fcm.v1.FcmError",
"errorCode"=>"THIRD_PARTY_AUTH_ERROR"}]}}
I'd expect the client to raise if the final retry wasn't successful, but as it stands it just returns the above error. Is there a specific reason why that's not the case or would a PR that changes this behavior be welcome?
The text was updated successfully, but these errors were encountered:
padarom
changed the title
Too many retries doesn't cause client to raise
Too many retries don't cause client to raise
May 19, 2020
In our case the client keeps receiving responses with code 401. The FCM authentication works fine, but the configured APNS key doesn't seem to be working temporarily, so the FCM servers aren't able to properly authenticate with Apple and just bubble the 401 back to the client. The response includes that information, but since it also happens to be a 401 it just keeps trying to refresh its access token until it times out.
firebase_cloud_messenger/lib/firebase_cloud_messenger/client.rb
Lines 24 to 30 in f96bcd6
I'd expect the client to raise if the final retry wasn't successful, but as it stands it just returns the above error. Is there a specific reason why that's not the case or would a PR that changes this behavior be welcome?
The text was updated successfully, but these errors were encountered: