Lines Matching refs:ID
51 <p>When a 3rd-party server posts a message to GCM and receives a message ID back,
64 a message with the same collapse key (and registration ID) stored and waiting for
95 invalidate the registration ID. Future attempts to send a message to that device
124 it should save the registration ID for future use, pass it to the
136 ID, as it is not guaranteed to work with the new version. Because there is no
139 ID is stored. Then when the application is started, compare the stored value with
143 <p>Similarly, you should not save the registration ID when an application is
144 backed up. This is because the registration ID could become invalid by the time
147 store that registration ID anymore—thus the application will not get more
155 recover from these situations. A canonical registration ID is defined to be the ID
156 of the last registration requested by your application. This is the ID that the
158 <p>If later on you try to send a message using a different registration ID, GCM
160 ID in the <code>registration_id</code> field of the response. Make sure to replace
161 the registration ID stored in your server with this canonical ID, as eventually
162 the ID you're using will stop working.</p>
183 <p>A registration ID (regID) represents a particular Android application running
195 ID or a different ID—there's no guarantee either way.</li>
230 <li>The GCM server marks the registration ID for deletion.</li>
233 <li>The 3rd-party deletes the registration ID.
240 <p>Note that it might take a while for the registration ID be completely removed
242 message ID as response, even though the message will not be delivered to the device.
243 Eventually, the registration ID will be removed and the server will get a
394 when requesting a registration. Finally, share the registration ID with your