-
Notifications
You must be signed in to change notification settings - Fork 84
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 Error Throws Exception #80
Comments
@Thomr77 it seems like we were always throwing errors when firebase returns non-successful response: However as we're now using their new API some statuses/behaviours changed. I can't tell.. |
@andrei-m-code cheers! It would be so convenient if it came back as an object (error) so that there is less code on the caller's side to take it apart. What do you think about replacing
with
And then just deserialize the response every time
Then it is ready to go for the caller. Could that work? I can add this code if this works for you - but I have not done that before so not sure - please advise. Thanks! |
That would be handy but I'd need to verify that the structure of the error is a constant to be sure we don't break anything. I'm fine if you open Merge Request with supporting links to the documentation. |
Hey @andrei-m-code! I just started with integrating the above code but then I saw that you have unified the results from SendAsync() with ApnSender and FirebaseSender into PushResult record. I think it is really great to unify these results, but I am not sure that I can add the above code now as it is only really working with Firebase. Please let me know how to proceed - thanks! |
@Thomr77 PushResult is a way to go. Let me know if you come across any issues. cc @StanDotNet |
@andrei-m-code - Okay sounds great. With these updates, you have anyway done pretty much what the above code would do! 😀 |
Hey @andrei-m-code! I have a small suggestion so the Firebase SendAsync() PushResult is more quickly consumable by the caller. Possibly, I could add more detail to the FirebaseError for the future. The changes are in two files - can I commit these for you to review? Please advise - thanks! |
@Thomr77 go for it! Thank you! |
Released. Thank you! |
@andrei-m-code - Awesome, thank you too! 😀 |
Hi,
When Firebase encounters an error then an exception is thrown - in previous versions it reported the error.
Call FirebaseSender.SendAsync(payload) with an invalid recipient token for example.
Thanks!
The text was updated successfully, but these errors were encountered: