0

In the documentation for push on Android it states that one has to implement the registration logic in a way that is capable of handling changes to the registration ID by Google. In the scenario I want to realize, this adds a lot of complexity, since I want to send push notifications from a build server, not an application server, and it looks like I cannot rely on the registration ID to be stable.

Has this actually ever happened to you that the Google push servers would send a new registration ID to your client, or is a case where Google simply want to reserve some flexibility for themselves? If it happened, how frequently? Ideally I would like to register my client application once, and then configure the build server with the static registration ID.

mxk
  • 43,056
  • 28
  • 105
  • 132
  • Did you already see this previous question: http://stackoverflow.com/questions/4265514/android-c2dm-registration-id – gnuf Jul 04 '11 at 18:19
  • Nope, thanks. So there is no exact answer to this then I suppose? (answers in that question thread just reiterate what's already in the official documentation) – mxk Jul 05 '11 at 16:25
  • The links I provided in my answer to that question contain posts from a Google employee writing in an unofficial capacity. Unfortunately, that's all we have to work with. For your application though, why can't you just rely on the client to send any updated registration ID to a central server, and have your build server read what the current value is? – gnuf Jul 05 '11 at 18:09
  • because that would require me to set up an application server with DB access and an API endpoint, which about quadruples the complexity of that project :-) – mxk Jul 06 '11 at 08:43

0 Answers0