Issue metadata
Sign in to add a comment
|
Push notifications from Twitter Lite PWA sometimes stop working |
||||||||||||||||||||||||
Issue descriptionChrome Version: 60.0.3107.3 (Official Build) dev (32-bit) OS: Android 7.1.2 NHG47N Device: Google Pixel What steps will reproduce the problem? (1) Add Twitter Lite as a home-screen icon and enable push notifications for it. (2) When Twitter pushes a notification about a popular tweet, tap the notification. What is the expected result? Expect reliable navigation to the tweet. What happens instead? Chrome frequently gets "stuck" after some period of time, after which all of these notifications will keep returning to a particular tweet, seemingly from an older push notification. It's not clear to me whether the PWA deliberately navigates to that older tweet, or whether that was the PWA's state, and it failed to do the navigation after reopening. I haven't found any way to get things unstuck except by rebooting. I'm pretty sure this is a bug in Chrome's implementation of push notifications and not a bug in the Twitter PWA, because these notifications work for a while and then completely stop working after a day or two. There are some similar open issues like Issue 534537 , Issue 594541 , and Issue 617414; this one affects a major PWA, so I'm filing it separately in hope that it'll be investigated promptly. Per earlier comments, not sure whether this is in the Push API or ServiceWorker. CC'ing people from older bugs. Here are a couple of Drive links to bugreports from my phone -- can only be accessed from google.com addresses. This one was taken after tapping a notification and instead the PWA opened an earlier tweet: https://drive.google.com/a/google.com/file/d/0B5DES7PYkZBLWmx6UFNiajQ3TkR0akRQQzdtSGFZaWw3QV9F/view?usp=sharing This one was taken after tapping a notification multiple times and doing so did nothing. After grabbing the bug report the app navigated to the tweet. This is probably the same problem as Issue 534537 : https://drive.google.com/a/google.com/file/d/0B5DES7PYkZBLcE9DZG0tRmtWeDV5ZUU0QWxzbEVFd0RiUERn/view?usp=sharing This is my only complaint with the Twitter Lite PWA.
,
Jun 1 2017
One more that just happened: tapping a notification for a tweet by @emackey took me to one by @Atrix256 that I tapped days ago. https://drive.google.com/a/google.com/file/d/0B5DES7PYkZBLMkxJTzRUQk1lRkNXdGEyeDNlYlJ1WnFwbjJ3/view?usp=sharing
,
Jun 1 2017
This might be related to Issue 725337 . In some situation, the renderer process might be possible to keep sleeping even though events is happening.
,
Jun 1 2017
Seems likely. Blocking this on the other bug. Feel free to duplicate it if it seems it's exactly the same issue.
,
Jun 1 2017
I'm not sure this is exactly same bug. The original report reports two problems: 1) tapping the notification brings you to an older tweet 2) tapping the notification does nothing It sounds likely for 2), but 1) feels different as we were able to connect to a running service worker and it successfully called Client.openWindow().
,
Jun 7 2017
Issue 726901 was closed. As per c#5, problem #2 might be solved by the fix, however, it might be different from problem #1. This still needs investigation once again.
,
Jun 7 2017
For what it's worth, I haven't seen this in the past few days. At this point, I'm running: 60.0.3112.10 (Official Build) dev (32-bit)
,
Jun 9 2017
,
Jun 15 2017
OK if it hasn't been seen in a while, maybe it really was issue 726901 . Please open again if you see more problems. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by owe...@chromium.org
, Jun 1 2017