-
Notifications
You must be signed in to change notification settings - Fork 72
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
Firebase Token Error response handling #74
Comments
This are the parent errorCodes, but there are specific for messaging. |
Sorry, there was another property. I have pushed a potential fix. |
ok looks good. That's what I would have expected. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm wondering about the error code handling of firebase.
See
notifo/backend/src/Notifo.Domain.Integrations/Firebase/FirebaseMobilePushSender.cs
Line 62 in ef9b635
There is a handling for error code "NotFound" and "InvalidArgument", but on firebase admin doc I can't find the notFound code. Instead for invalidating the token we should wait for "Unregistered". I would expect that this is the also the only response that should trigger an invalidation. All other errors are not related to the life of the token.
https://firebase.google.com/docs/reference/admin/dotnet/namespace/firebase-admin/messaging#namespace_firebase_admin_1_1_messaging_1ac3482b9d4581255dee08b81ac3f677c9
The text was updated successfully, but these errors were encountered: