New issue
Advanced search Search tips

Issue 648742 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

GCM push notifications buffered after computer waking up from sleep

Reported by kedao.w...@salesforce.com, Sep 20 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Install any extension that supports GCM push notification
1. Put Macbook Pro to sleep.
2. Trigger 2 push notifications
3. Wake up laptop from sleep.
4. Push notifications arrives 4 minute after I woke up laptop (this time, right after when a 3rd push notification is triggered).

What is the expected behavior?
GCM push notifications arrived during sleep should be delivered immediately after laptop wakes up.

What went wrong?
GCM push notification delays in appearing, after laptop awakes from sleep. Sometimes the old notifications will only deliver when a new notification gets triggered after awake.

WebStore page: 

Did this work before? Yes see "other comments"

Chrome version: 52.0.2743.116  Channel: stable
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0

This same issue was fixed before: https://bugs.chromium.org/p/chromium/issues/detail?can=2&q=gcm&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&id=526910&thanks=526910&ts=1441076507#makechanges

I believe this worked after this fix above.
 
Cc: peter@chromium.org zea@chromium.org
Components: Services>CloudMessaging
Hey, please take a look and see if this is something we can fix.

Comment 2 by owe...@chromium.org, Jan 23 2017

Status: WontFix (was: Unconfirmed)
This looks like a dupe of the commonly reported issue of notifications getting 'stuck' somewhere and not flushed. I understand this is part of the notifications system, not GCM itself and is likely to be fixed when we move to native notification centers.

I can't see the main issue tracking this so can't mark as dupe so marking as WontFix as it's a well known issue.

Sign in to add a comment