Offline Prefetching notifications might be firing more often then they should |
|||
Issue descriptionI noticed a couple of cases where the offline content notification was triggered during the night. This seemed strange for a few reasons: * I have many Chrome channels installed on my device but only one of them fired the notification in each isolated occasion (Dev and Canary). * It is very unlikely that my device connectivity would be kept as offline for such a long time because of the redundancy of having both wifi and the phone carrier network available. If this proves to be an actual misfire this means we would be showing notifications when the user doesn't actually needs to be informed about offline content.
,
Nov 8 2017
,
Nov 28 2017
I second the Carlos' observations. In my case, I also have 2 prefetch-enabled instances of Chrome, Dev and Canary, but I only open Canary from time to time so the Dev does not get any Zine updates and therefore never prefetches anything. Canary often shows me an offline prefetch notification which pops up around 7am in the morning, even though the phone always has WiFo and cellular connectivity.
,
Nov 28 2017
I generated a few Android bug reports generated right after I noticed that notifications had been created when I thought they shouldn't. Tomorrow chili@ and I will take a look at them and see if we can find some clue.
,
Nov 29 2017
Analyzing these reports is a "needle in haystack" game, at least for first comers like us. However we did find what seems to be a correlation between battery saver being active and the offline detection background task behaving as if it was detecting the phone as being offline. But the OS still seemed to think the device was connected through out that period. chili@ will run a few tests to see if battery saver has any effects over our checking for connectivity. |
|||
►
Sign in to add a comment |
|||
Comment 1 by carlosk@chromium.org
, Nov 7 2017