GCM CCS (XMPP) Canonical ids

[Sebastian Bendeich]

Hello everybody,

does anybody know if the "canonical id" mechanism, which is described in the GCM-over-HTTP documentation, also exists in the CCS (XMPP) protocol??

My first guess would be, that the "from" value in the ACK message does the job of "canoncial id", but it's not documented anywehere :-( 

On the other hand, the "from" value is always present in the ACK message, whereas the "registration_id" in GCM-over-HTTP is only present in the response, if there is a canonical id.

I couldn't test it, because since Google approved my account for using CCS (XMPP), I couldn't enforce a registration id change....

Can somebody confirm my guess? Or how do you handle the "canonical id" problem at CCS (XMPP)?

Regards,

Sebastian

[grebulon grebulonovich]

Any news on this?

[Tarak Gudipati]

Looks like its not the case, From is always present in xmpp ack & from has the value of the registrationID where the message was sent(To of the request).

I have got an ack from xmpp for the registrationID which is not valid without any additional information where as HTTP sends the new canonical ID ins response for the same registration ID.

pleas let me know if you have found a way to get the canonical ID in xmpp response.

[Roman Skvazh]

Same problem. I need to clean database from old canonical tokens, but with CCS there is no way :(

среда, 10 декабря 2014 г., 20:07:02 UTC+3 пользователь Rahul написал:

[Tingmui Li]

Thank you all for the feedback. 

This is in our feature list and we will announce this as soon as it becomes available.

[Tingmui Li]

Canonical ID for XMPP support has been added.

See https://developers.google.com/cloud-messaging/server-ref#interpret-downstream Table 7 for reference