Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

RestClient uses the deprecated registration_ids message property #84

Closed
secondsun opened this issue Jul 31, 2015 · 6 comments
Closed

RestClient uses the deprecated registration_ids message property #84

secondsun opened this issue Jul 31, 2015 · 6 comments
Assignees

Comments

@secondsun
Copy link

The sender in the rest client uses "registration_ids" instead of "to" when sending a single message.

In the target section of the downstream doc this field is said to be deprecated for general use.

@secondsun
Copy link
Author

Additionally, because the "to" field is unsupported the rest-client can't be used to send topic messages.

@kroikie
Copy link
Contributor

kroikie commented Oct 1, 2015

registration_ids is not deprecated.

@kroikie kroikie closed this as completed Oct 1, 2015
@secondsun
Copy link
Author

@kroikie

Then what does "Though for general purposes it is deprecated, you can use registration_ids as a target for multicast messages to more than one device (up to 1000)." mean on https://developers.google.com/cloud-messaging/concept-options#notifications_and_data_messages?

@kroikie
Copy link
Contributor

kroikie commented Oct 1, 2015

Thanks @secondsun for the heads up on that, these docs are misleading and should be clearer, but registration_ids is not deprecated.

@secondsun
Copy link
Author

@kroikie Gotcha. Where is the issues page for docs? I would like to file/track this bug there.

@silvolu
Copy link
Contributor

silvolu commented Oct 1, 2015

@secondsun we have an internal issue open for this. In the future, if you want to send feedback about the docs you can use the Send Feedback button that you can find on the right of the docs' navigation bar.
GCM doesn't have a public issue tracker (this one is not meant to be for gcm product or docs, just for the content of this repo).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants