Issue metadata
Sign in to add a comment
|
Even Listener Push gets called multiple times for one message
Reported by
richie3...@gmail.com,
Apr 25 2018
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Steps to reproduce the problem:
1. Send a push notification to a android mobile or chromium windows version.
2.If the notification is sent to lots of users and your server becomes busy and takes bit of time to send the message when requested, multiple times Push Listener function is called.
3. Due to which there is increase in load for server as multiple request is sent from the same user and many people get the same message multiple times
What is the expected behavior?
Push Event gets called only once
What went wrong?
self.addEventListener('push', function(event) {
console.log('inside push')
});
This function gets called multiple times for one push
Did this work before? Yes Not sure
Does this work in other browsers? Yes
Chrome version: 65.0.3325.181 Channel: n/a
OS Version: OS X 10.12.0
Flash Version:
,
Apr 26 2018
richie3355@ Thanks for the issue. Request you to provide a sample file/test URL where this issue can be reproduced and also a screen cast of the steps followed which will be helpful in further triaging of the issue. Thanks...
,
Apr 26 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 27 2018
richie3355@ Thanks for the update. As per comment #3, we don't have Firebase setup done to test this as of now. However, would it be possible to attach sample html file with the above test case for the ease of repro on Desktop and check where it regressed. Also requesting someone from Blink>PushAPI team to look into this issue and help in further triaging. Thanks..
,
Apr 27 2018
thanks for the update somehow it got sorted. Now only getting one message per request.
,
Apr 27 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 30 2018
richie3355@ Thanks for the update. As per comment #6, can you please confirm if this issue can be closed? Thanks..
,
Apr 30 2018
When this happens again, could you please record (and screenshot) the data on the following page so that it's easier to see what's going on?
chrome://gcm-internals
,
Apr 30 2018
the network tab screenshot which i sent was of chrome://gcm-internals only. The issue got resolved somehow and you can close the issue now. Thanks |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Apr 25 2018