On Tue, Sep 17, 2013 at 2:15 PM, Daniel Passos <daniel(a)passos.me> wrote:
I was thinking about it. That would be the responsibility of the
I think the lib should give an error msg, and do the log (+retry).
The app should be able, I think, to responsed to that error msg
Btw, any thoughts?
On Tue, Aug 27, 2013 at 12:59 PM, Summers Pittman <supittma(a)redhat.com>wrote:
> So with GCM and Android, Google may decide to update the devices token.
> The device will receive a Intent saying that the token has changed and
> it needs to eventually update the remote server's data before the token
> Right now the application checks the device id on startup and
> reregisters if there is a change. If the user doesn't interact with the
> applicaiton for a long period of time and the device token changes he
> will eventually stop receiving messages.
> Ideally, I would think that handling this as soon as the intent comes in
> would be great. However, how should failures to reregister be handled?
> My easy answer is Log and retry with exponential backoff (and maybe send
> a error message).
> aerogear-dev mailing list
aerogear-dev mailing list