Issue metadata
Sign in to add a comment
|
MessageCenter Notifications do not always display |
||||||||||||||||||||||||
Issue descriptionChrome Version: 61.0.3118.0 OS: Platform 9576.0.0 veyron_minnie For a few months our component has successfully been displaying notifications to the user via MessageCenter::AddNotification (https://cs.chromium.org/chromium/src/chrome/browser/chromeos/net/tether_notification_presenter.cc?l=127). About 2 or 3 weeks ago, I noticed that notifications were no longer displaying. The extremely odd thing about this is that our notifications do display if the AddNotification callsite is changed. Take our TetherNotificationPresenter::NotifyMultiplePotentialHotspotsNearby() method (linked above) for example: this method is called indirectly through a callback from the system. However, if I place the method call in our setup code (called indirectly from UserSessionManager), the notification displays. It seems that notifications are only displaying for us when we try to display them during system setup / user login. Why does the callsite of MessageCenter::AddNotification matter (is it a process issue?)? Is MessageCenter not always available (even if MessageCenter::Get() is non-null)? Are certain flags being attached to Notifications that would prevent them from displaying?
,
Jun 6 2017
yoshiki@, do you have any ideas on this issue?
,
Jun 6 2017
My first assumption is threading. Calling message center methods on non-UI thread may break something. It looks NotifyMultiplePotentialHotspotsNearby() might be called on dbus-related thread and it may cause the issue?
,
Jun 6 2017
I placed print statements checking the value of content::BrowserThread::CurrentlyOn(content::BrowserThread::UI) all throughout our code, including the callsite where NotifyMultiplePotentialHotspotsNearby() is called. In all places, content::BrowserThread::CurrentlyOn(content::BrowserThread::UI) returns true. Is it possible that the check is incorrect?
,
Jun 6 2017
I tested for this issue on a sentry running 9623.0.0, 61.0.3123.0 -- the issue is not present (notifications appear just fine). We also tested on a veyron_minnie running 9588.0.0, 61.0.3123.0 -- the issue is also not present. Weirdly, it seems that the test image was causing this issue. It seems to be resolved now.
,
Jun 7 2017
,
Aug 2 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by hansberry@chromium.org
, Jun 5 2017