Home/ Questions/Q 7831787
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T11:53:07+00:00

We have a working app and server that uses C2DM to push messages to

  • 0

We have a working app and server that uses C2DM to push messages to Android devices.

Two days ago one of our test devices stopped getting pushes from the server.

  • The deviceRegistrationId the server sends to seems to be updated and correct, the device has a network connection, and google apps using C2DM like Gtalk work properly on it.

  • The server gets a success response from Google’s C2DM servers with a proper response of “id=0:133467...61+ac67f...66“

  • The device was accepting pushes properly before then.

  • Our app is live on the market and used daily by lots of users, and we haven’t received any similar complaints by users (not that it means it doesn’t happen to some of our users)

Any ideas what can be further check to understand this?

Is there a way to use the id received from the C2DM server to check what happened to a specific message?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I’m not aware of any reporting to track messages.

    The first thing I’d check is that the Registration ID you’re sending messages to is still the one the device is using – if they are mismatched that could cause what you are seeing.

    I have seen several devices just suddenly stop receiving C2DM messages. In our case, restarting the device usually fixed it.

    Another scenario I’ve seen is devices on particular networks not receiving messages (specifically some wifi networks).

    • 0