A simple restart resolves the GCM notifications duplication problem...

[Michael Azerhad]

Hi,

Many users use my Android app and receive some notifications through my architecture:  android app <------>server <-----> GCM`

Yesterday, they complained about duplicated notifications arriving on their device. 

Indeed, server logs showed the duplicates providing directly from GCM.

I directly thought about the famous canonicalId mechanism that would prevent multiple registrations to cause trouble.

However, since my notification strategy makes use of a composite key User/RegistrationId, I can assert that I always use the last registrationId. 

So what I simply do is to restart my server (client of GCM), and the problem magically disappears. No more duplicates !

My question is: how did my server restart impact the GCM behavior?  

                         May the fact to kill the GCM connection resolve the whole?

I'm very curious, 

Thanks a lot

[Diego Giorgini]

Hi there!

Could you provide some references (registration-id, message-id) which experienced the problem?
(Recent data would be better)

Also can you detail more your architecture?
Which API are you using? dowstream (cloud-to-device), upstream (device-to-cloud), http, xmpp, standard gcm messages, user notification messages.

Thanks
- Diego

--
You received this message because you are subscribed to the Google Groups "android-gcm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-gcm...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/428af0dc-3d4f-454c-9dd8-c3dbcec0377e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.