rs / pushd

Blazing fast multi-protocol mobile and web push notification service
MIT License
1.16k stars 224 forks source link

GCM Automatic unregistration for subscriber (Need help. We are in production) #153

Closed akkina9 closed 7 years ago

akkina9 commented 7 years ago

I first noticed this problem when I started using pushd for android. The problem was fixed once we started using GCM Registered ID instead of device id.

Now, for some reason after registering the device, subscribing to events, unsubscribing to events, and re-registering a few times (we do this every time the user logs in), we start seeing the automatic unregistration of the subscriber problem when notifications are pushed to the device. And once this happens, when we try to re-register, we get a new subscriber id and it keeps unregistering the new subscriber every time a push notification is sent. The only way to get it to work again is to re-install.

Any idea what might be happening? What are all the instances when the subscriber gets automatically unregistered?

Should I try installing the latest version of redis and pushd?

akkina9 commented 7 years ago

Any input will be appreciated...

akkina9 commented 7 years ago

Upgrading to latest pushd did not help. @rs any input will help.

akkina9 commented 7 years ago

I added some log to gcm.coffee and I see the error 'NotRegistered' is causing the issue. Have to dig in little more. Any input will help.

akkina9 commented 7 years ago

The issue was at our end. Our app was un-registering the device when ever the users logs off. Once we stopped doing it, it all is working.