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
{{ message }}
This repository has been archived by the owner on Oct 27, 2019. It is now read-only.
I just finished adding initial support for device group messaging in f1b3161. I would appreciate it if you could test it out and provide any feedback or issues you may encounter.
It's working great, thanks for the enhancement. I only have few questions.
1- Are you implementing the send method for group operations?
2- Shouldn't we make the SENDER_ID an attribute of the Sender class?
3- GCM sometimes returns 200 but the operation is not fully successful. For example, when we try to create a group that already exists we get a HTTP 200 code and a message: ''{"error":"notification_key already exists"}'". There are similar cases like this one. Should we catch these "errors" ?
Please let me know if you need any help with these improvements!
Yes, the responses are different and are not parsed correctly right now. Either the send method needs to parse either possible response or there needs to be a separate send method.
Yes, I think that makes more sense in the long run.
I ran across this when adding support for groups, but I didn't notice that they were 200 responses. It's unfortunate that part of their API respects status codes and part of it does not. The only solution would probably be to check for the presence of the top level error key when deciding if the request was a success or not.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi! First of all, thanks for the great package.
I would like to know if you are planning to support registering and sending messages to GCM Group.
As you can see here: https://developers.google.com/cloud-messaging/notifications to support Group messages we need to be able to:
The text was updated successfully, but these errors were encountered: