GCM not working since Friday?

[Aleksander Świtalski]

On Friday I stopped getting messages from GCM, the REST service does not return any error.

Just the listeners are not called in the extension anymore...

I double-checked channel ids, tested on several Chrome instances on different machines and using different end user accounts.

Is there some outage now?

Cheers.

Alex

[Dmitry Titov]

Hi Aleksander!

It doesn't show on our end that there is an outage or something else big...

Can I ask you some questions:

- What version of Chrome are you using?

- When you open chrome://sync-internal and go to "Notifications" tab, is the Status like this:"State: INVALIDATIONS_ENABLED"?

- Reboot/restart/connect to another network doesn't help?

--
You received this message because you are subscribed to the Google Groups "GCM for Chrome feedback" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gcm-for-chrome-fe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aleksander Świtalski]

Thank you for your reply.

Today I tried logging out and in, it did not help. Then I uninstalled and installed the same extension again - and it finally helped.

This problem happened to all users using this extension at the same time, no Chrome updates were run, nothing really changed.

It just stopped working for everybody.

Tomorrow I'll try the same "solution" on different computers using different Google accounts and will see if the reinstallation helps everywhere.

Before doing that I'll check the status on the sync-internals config page to see if any problem is reported there and will send the update.

[Aleksander Świtalski]

On one computer, where notification don't work at all - on chrome://sync-internals page (Notifications tab) the status is "TRANSIENT_INVALIDATION_ERROR".

What does it mean? What can I do with it?

[Aleksander Świtalski]

I'm still having problems with delivery of messages to my Chrome extension.

The status says "INVALIDATIONS_ENABLED", I even inspected the network traffic with Wireshark and XMPP messages are delivered to my machine, but still the listener in the extension is not invoked...

How can I check if Chrome gets these messages?

For sure my extension does not get them, but perhaps Chrome itself gets them, just does not dispatch to the extension... ?

Cheers.

[Dmitry Titov]

Are you absolutely sure you register the listener in the extension (crome.pushMessaging.onMessage.addListener) every time the app starts (in initial JS script of background page)? I'm pretty sure you do, but just in case... Also, make sure you didn't change the app id somewhere in the process - that would change the channelId. It probably would prevent the messages to even come to your machine then, because it won't be registering for the old channelId on Chrome startup, but who knows, it sometimes happens when developers have a test and release app versions installed on the same machine and they have different Ids so only one of them wakes up and it's not the right one...

If you see notifications coming over the wire, they should definitely come into that event. Unfortunately, there is no diagnostic page or log that is available to see how Chrome processes the incoming messages...

Are the XMPP messages looking like the right push messages? If they are delivered, that means some app in your Chrome is installed with proper app id/user profile combination.

One reason the app can miss them is if it ever started w/o registering the onMessage event listener. It should do it every time its background page is activated, from the initial script of the background page, not from another event handler.

I wonder if it gives you more food for thought and checks... Let me know!

--

[Aleksander Świtalski]

I checked everything again and indeed I found one corner case where the listener was not registered and this caused problems from time to time.

Thanks for the comprehensive explanation!

Cheers.

[Dmitry Titov]

Great! I'm glad the issue is found!

Dmitry