New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 759751 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Not all pushes processed when user goes from offline to online

Reported by ameya.ka...@gmail.com, Aug 28 2017

Issue description

Steps to reproduce the problem:
1. Register a new push subscription (I have tried with my organization's account, https://gauntface.github.io/simple-push-demo/ makes things simpler to reproduce) on Chrome - Android
2. Shut down your network connections (or go to Airplane mode)
3. Send multiple push notifications (say N in number, N > 1; try a big number) to your registration (the app by @gauntface conveniently gives the necessary curl commands)
4. Open chrome://gcm-internals on your Android device
5. Re-enable your network connections and observe the Receive Message Log on chrome://gcm-internals

What is the expected behavior?
N notifications are received

What went wrong?
Most of the N notifications are not processed. I mostly get only 1, and at rare times, 2 or 3 notifications. When one sends multiple pushes when the device is online, all notifications are received. Attached is a screenshot of the gcm-internals log when I sent out 5 messages, and received only 1

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 60.0.3112  Channel: stable
OS Version: 7.0.0
Flash Version:
 
Screenshot_20170828-231451.png
85.4 KB View Download
Adding for more information, the behavior is as expected on Chrome Desktop (V53, RHEL). I have tried this with both FCM and the older GCM method of sending pushes. I have not added the Topic header (or a collapse_key field) for any of the requests.
Cc: mattgaunt@chromium.org
Cc: sandeepkumars@chromium.org
Labels: Needs-Feedback TE-DesktopTriage
Tested the issue using #60.0.3112.107 on Android 7.0.0 Samsung Galaxy S6 Edge Plus and was unable to reproduce the issue as per the steps mentioned below.

1. Launched Browser.
2. Navigated to https://gauntface.github.io/simple-push-demo/ page
3. Enabled Push Notifications and pushed 10 to 15 notifications 
4. Turned off Wifi
5. Navigated to chrome://gcm-internals 
6. Turned on Wifi and observed N notifications are received

@ameya.karve: Could you please provide us the details of your device and chrome://version, and if possible please add a screen cast for further triage of the issue.

Thanks!!
Sandeep, Step 4 should happen before Step 3; I assume you sent the notifications after turning off Wifi anyway.

Let me get a screencast and attach
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 30 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
@Sandeep Attaching the screencast.
I am on a Moto G5 Plus, Android 7.0.0

At the start of the clip, I have airplane mode on.

I sent 5 curl requests to send a push to the device.
Then, I turned Airplane mode off. The gcm-internals received log is shown; a single push entry was received and captured


screencast-chrome-final-480p.mov
3.2 MB Download

Comment 7 by peter@chromium.org, Sep 1 2017

This seems to work fine on my devices. Could you check the GCM diagnostics tool on your device to see what's going on?

Go to the Phone app and dial *#*#426#*#*, then click on [Events]. Reconnect to the network and check how many messages are being send to the Chrome package.

Note that only a single notification should be shown in either case, but that doesn't affect chrome://gcm-internals/ either.
@Peter I am able to see all the N messages on *#*#426#*#*

chrome://gcm-internals still shows only 1 though
I tried to reproduce this on a Nexus 5, but was unable to do so. Might be something to do with the device.

Let me try this with a bunch of device models and get back on the thread
Cc: msrchandra@chromium.org
Labels: -TE-DesktopTriage Needs-triage-Mobile Triaged-Mobile Needs-Feedback
@ameya.karve -- Could you please update Chrome to Latest Stable and let us know if you are still seeing the issue.
Thanks in Advance.
Status: WontFix (was: Unconfirmed)
***Bulk Edit***

There is no updates in the past few months, closing now. Feel free to reopen if needed.

Sign in to add a comment