in my onCreate of the main avtivity i put that code
Intent registrationIntent = new
Intent(com.google.android.c2dm.intent.REGISTER);
registrationIntent.putExtra(app, PendingIntent.getBroadcast(this, 0, new
Intent(), 0)); // boilerplate
registrationIntent.putExtra(sender, bermane...@gmail.com);
Given that it's in your onCreate of the main activity, I'd say it's sent
every time onCreate is called on your main activity, unless you've added
additional logic you're not showing.
On Thu, May 17, 2012 at 3:02 AM, Eyal Berman bermane...@gmail.com wrote:
in my onCreate of the main avtivity i
did the registrationId is changing or it is always the same until the next
instalation?
On Thursday, May 17, 2012 4:55:07 PM UTC+3, Dallas Gutauckis wrote:
Given that it's in your onCreate of the main activity, I'd say it's sent
every time onCreate is called on your main activity, unless
The registration id changes every time you request it. Additionally, it may
change periodically without request. Make sure the server always receives
the latest registration id broadcasted.
See https://developers.google.com/android/c2dm/#registering for more info.
On Thu, May 17, 2012 at 11:35
So I need to save registrationid on app db and every some time to check it
against Google?
On 17 במאי 2012 18:42, Dallas Gutauckis dall...@gmail.com wrote:
The registration id changes every time you request it. Additionally, it
may change periodically without request. Make sure the server
I recommend that you save it in the application's storage and only attempt
to register again for an id when the registration id is no longer valid.
The documentation I linked to explains that you may get an unregistration
REGISTRATION' intent which would be the registration broadcast without an
my architecture is like this:
the app onCreate send check the local storage for registrationId - if the
registrationId is empty it register and send the registrationId and
devaiceid to a webService that store it on DB
then a service is look in db for new messages and if there are he push them
The app is the responsible party for getting a registration id. You could
at any point notify your app as part of an API response that the server
doesn't have a registrationId, but if you're supporting Android OS versions
2.2, those phones won't even be capable of getting a registrationId.
On
We have some questions regarding the Android Cloud to Device Messaging
Framework (C2DM) services.
1.Regarding to enabling C2DM section in
http://code.google.com/intl/zh-TW/android/c2dm/,
°ßIf the registration is successful, the C2DM server broadcasts a
REGISTRATION Intent which gives
9 matches
Mail list logo
