New issue
Advanced search Search tips

Issue 849241 link

Starred by 8 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Chrome , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Service worker's Push/Sync locally triggered events don't work

Reported by cornel.c...@gmail.com, Jun 4 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36

Steps to reproduce the problem:
1. Open "chrome://serviceworker-internals/"
2. Inspect the demo service worker, adding breakpoints inside the "push"/"sync" event handlers
3. Open Dev tools(F12)
4. Go to the "Application" tab
5. Go to "Service Workers" section
6. Send a "push" message to the service worker
7. The breakpoint is not hit

What is the expected behavior?
The breakpoint should get hit

What went wrong?
The breakpoint doesn't get hit

Did this work before? Yes ?

Chrome version: 67.0.3396.62  Channel: stable
OS Version: 10.0
Flash Version:
 
Cc: pbomm...@chromium.org falken@chromium.org
Labels: Needs-Triage-M67
May be related to  bug 848645 ?
Cc: dgozman@chromium.org
Components: Blink>ServiceWorker
Labels: Needs-Feedback
Looks unrelated. cornel.chintoi: Can you provide the "demo service worker" from comment 0?
Here is a demo for service workers, with push event listeners: https://gauntface.github.io/simple-push-demo/
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 4 2018

Labels: -Needs-Feedback
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
Owner: eostroukhov@chromium.org
Status: Assigned (was: Unconfirmed)
Labels: ReleaseBlock-Stable M-67
If this is a regression aren't we suppose to mark the bug as stable blocker, currently working on another bisect and will try to reproduce and get bisect once done with other bug.
Labels: -ReleaseBlock-Stable
Not a blocker.
Requesting priority to be raised as its a blocker in debugging push service workers and very annoying to work around it 
I'm also running into the same issue on MacOS, Chrome version 67.0.3396.99 and 70.0.3503.0
Owner: hhli@chromium.org
Labels: OS-Chrome OS-Mac
I can also reproduce on Mac, CrOs while doing the following codelab parts:

https://codelabs.developers.google.com/codelabs/debugging-service-workers/index.html#6
https://codelabs.developers.google.com/codelabs/push-notifications/#6
Labels: Needs-Feedback
FYI this works for me on 73.0.3664.0 Canary on Mac. Is it still broken for you?

Sign in to add a comment