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

Issue 594541 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome notifications don't work

Reported by gferrett...@gmail.com, Mar 14 2016

Issue description

Steps to reproduce the problem:
1. Visit websites that allow notifications (e.g. Facebook)
2. Allow and approve notifications from websites when Chrome correctly asks if I'd like to get notifications
3. 

What is the expected behavior?
I should get notifications exactly as I get them in Chrome on Windows/Chrome OS

What went wrong?
I never get any notification

Did this work before? No 

Chrome version: 49.0.2623.91  Channel: stable
OS Version: 4.3.0
Flash Version:
 
Cc: peter@chromium.org mvanouwe...@chromium.org
Components: -UI UI>Notifications Blink>PushAPI Platform>Apps>PushMessaging

Comment 2 by peter@chromium.org, Mar 15 2016

Have you perhaps disabled notifications for Chrome in the past?

You can find this out by going to Settings > Apps > Chrome > Notifications. If that's set to block everything, it won't be able to show you any.
No they are active and have ever been.

Il 23:52 Mar 15/Mar/2016 peter@chromium.org via Monorail <
monorail@chromium.org> ha scritto:

Comment 4 by peter@chromium.org, Mar 16 2016

Components: -Platform>Apps>PushMessaging
Labels: Needs-Feedback
Okay, thank you! A few more questions:

  - Which Android device do you use?
  - Does the notification demo page work for you?

https://tests.peter.sh/notification-generator/

  - If so, does the following push demo work for you?

https://johnme-gcm.appspot.com/chat/

  - If it doesn't, try opening a second tab for "chrome://gcm-internals/", click the "Start Recording" button, and try the push demo again in the original tab. Then look at what the gcm-internals tab says in its log files.

Sorry that this is a bit technical, but it'd help us tremendously in tracking down why this is happening for you!
Hello and thanks.
I have a galaxy S3 (I know.. Quite old..).
Yes both work. With them I do see notifications.

And days ago I saw One random from new scientist website. Just One. While
on my laptop I see always especially for facebook.

Il 18:45 Mer 16/Mar/2016 peter@chromium.org via Monorail <
monorail@chromium.org> ha scritto:
All settings are active of course. I also browsed into flags to check all
possible causes. I downloaded chrome beta fresh and got Facebook logged in.
Nothing.
Maybe is my old phone, it's chrome makes some odd things. E.g. i have
another bug as it doesnt play YouTube videos (in chrome).

Il 18:57 Mer 16/Mar/2016 Giovanni Ferretti <gferretti80@gmail.com> ha
scritto:
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 16 2016

Labels: -Needs-Feedback Needs-Review
Owner: peter@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "peter@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by peter@chromium.org, Mar 16 2016

Cc: owe...@chromium.org
Components: -UI>Notifications
Labels: -Needs-Review
The S3 has a gigabyte of RAM, so it's not that low end either. It /should/ just work. I wonder if it's perhaps Facebook that for some reason chooses to not send messages to your device?

A second failure reason I could think of is that Chrome wasn't able to start. Unfortunately there's not a whole lot we can do there.
But it doesn't work on any other website so I don't think it is facebook.
Thanks anyway :) next one will be a nexus..

Il 20:10 Mer 16/Mar/2016 peter@chromium.org via Monorail <
monorail@chromium.org> ha scritto:
Hi, FYI I just got a Chrome notification from New Scientist website. So
well, it actually works, partly.
Cc: -mvanouwe...@chromium.org

Comment 12 by peter@chromium.org, Jun 28 2017

Status: Fixed (was: Assigned)
Closing following #c10. Hope it still works for you! :)

Sign in to add a comment