Lines Matching refs:ID
185 <td>Unique ID (number) identifying the multicast message.</td>
197 <td>Number of results that contain a canonical registration ID. See
204 ID in the request, its result is listed in the same index in the response) and
210 message but it has another canonical registration ID for that device, so sender
229 <li>If <code>registration_id</code> is set, replace the original ID with
230 the new value (canonical ID) in your server database. Note that the original ID
240 ID from your server database because the application was uninstalled from the
243 <li>Otherwise, there is something wrong in the registration ID passed in
253 The first line is always available and its content is either <code>id=<em>ID of
256 has the format of <code>registration_id=<em>canonical ID</em></code>. The second
269 <li>If it is <code>NotRegistered</code>, remove the registration ID from
283 <dt id="missing_reg"><strong>Missing Registration ID</strong></dt>
284 <dd>Check that the request contains a registration ID (either in the
289 <dt id="invalid_reg"><strong>Invalid Registration ID</strong></dt>
290 <dd>Check the formatting of the registration ID that you pass to the server. Make
291 sure it matches the registration ID the phone receives in the
297 <dd>A registration ID is tied to a certain group of senders. When an application
304 <dd>An existing registration ID may cease to be valid in a number of scenarios, including:
312 <li>If the registration ID expires. Google might decide to refresh registration
318 For all these cases, you should remove this registration ID from the 3rd-party
370 If you want to confirm the validity of a registration ID, you can do so by
371 replacing "ABC" with the registration ID.
415 A message was addressed to a registration ID whose package name did not match
441 with 3 messages successfully processed, 1 canonical registration ID returned,
460 <li>Second message: should be resent (to registration ID 8).</li>
464 <li>Fifth message: success, but the registration ID should be updated in the
466 <li>Sixth message: registration ID (42) should be removed from the server database