Unable to open Ads from Notification center
Alarm Only in Windows OS
Clicking on the notifications within the notification slide, just dismisses the banner without opening brave or displaying the ad.


The user should be able to open the Ads
Always
Brave | 0.63.40 Chromium: 74.0.3729.61聽(Official Build)聽beta聽(64-bit)
-- | --
Revision | 5df2c8936783bd7575987e45d72a92fcf528496b-refs/branch-heads/3729@{#645}
OS | Windows聽10 OS Build 17134.523
The issue is reported by the community
https://community.brave.com/t/unable-to-open-ads-from-notification-area/49199/4
@brave/legacy_qa @tmancey
https://bravesoftware.slack.com/archives/C43LW5U2H/p1555318060044600?thread_ts=1555302183.044200&cid=C43LW5U2H
Comments added in above slack thread:
using undocumented and unsupported methods it is possible to detect the status of Focus Assist.
@tmancey is investigating the issue.
I'm running win10 x64, with Focus Assist set to Alarms Only, and am observing the notifications in the OS Notification Tray.
Brave | 0.64.47
Chromium: 74.0.3729.61聽(Official Build)聽dev聽(64-bit)
-- | --
Revision | 5df2c8936783bd7575987e45d72a92fcf528496b-refs/branch-heads/3729@{#645}
OS | Windows聽10 OS Build 17134.706
Including a screenshot to illustrate as well.
@lukemulks , yes, the notifications are collected in the notification tray. However, they cannot be opened. Clicking on them just dismisses them without showing any ad.
+1 from Community too:
https://community.brave.com/t/notification-enabled-but-not-working/49594/63
Is there any particular reason we have this set to P4? Windows users are having enough trouble with ads/notifications as it is -- sucks to finally get them up and running only to not be able to view the ads. @rebron
@Brave-Matt I didn't set priority for this issue. I'm guessing that focus assist setting isn't a default windows setting and therefore fewer users are affected. Looks like @tmancey is looking at it though.
Notably, the ad notification will many times not open when the notification is clicked from the action center, even if "Focus Assist" is not enabled. Clicking on the floating ad works correctly, but once that panel is gone, it seems that clicking on the ad notification from within the action center slide out is generally borked.
Steps to reproduce (with default ad center settings, no focus assist)...
A few users in Community troubleshooting thread reporting this as well:
https://community.brave.com/t/brave-ads-windows-10-troubleshooting/56730/13
@jsecretan should we reprioritize this to maybe a P3? Seems like we're getting more +1 from Win users who are running into this. Imagine we'll want to get this fixed sooner than later.
i've been wondering about this since installing Brave almost a week ago or so. apparently i've missed out on about 330 ads so far, and i couldn't figure out why until i finally opened the notification center (which i basically never use) and saw all the ads, started clicking on them, and nothing happened.
@alefnull @kjozwiak @jsecretan We have identified an issue where if an Ad notification is shown and the user quits the browser, Ads will no longer open when clicked. We are working on a fix for this issue and investigating the steps reproduced by @rivy. @alefnull did you quit the browser?
@tmancey i actually rarely close my browser, and most of the times that i've clicked on the notifications in the notification center, my browser has been open, and nothing would happen. however, since posting my last comment, the few that i've clicked have actually opened successfully. so i'm not sure what happened, as i haven't done anything differently on my end, but it does appear to be working for me now.
@alefnull Thank you for the update
User also reported clicking on arrow thinking it would open up the ad when instead it closed the ad. This is confusing UI/UX, investigate further and discuss with UX
Clicking the arrow to initiate "move to the notification center" is normal.
In my experience, the usual windows notification idiom with most applications is to click on the message box to open the notification or click the arrow to dismiss it to the notification center. Clicking the upper right 'X' within the notification center should completely dismiss the notification, deleting it.
All of that is working correctly.
But, when in the notification center, clicking the notification doesn't open Brave and display the ad if the ad moved directly to the notification center by "focus assist" or by clicking the arrow on the desktop panel notice to move it into the center. That's the problem this issue points out.
@rivy thank you, much appreciated
For the last few weeks, I don't remember seeing any ads at all while in "focused" mode. I hope that's not the way you are going with this... I'd like to have the ads but see them at my desired times.
IMO, they should just be like normal notifications and pull up the ad in-browser whenever clicked upon.
What revision will this go out in?
My current version updated last night and this is still broken.
@rivy This fix is currently only in 1.3, are you able to test 1.3 (currently Nightly build), please? Thanks
give me link download
@riswyre @rivy https://brave.com/download-nightly/
but no ads Version 1.3.39 Chromium: 78.0.3904.108 (Official Build) nightly (32-bit)
but no ads Version 1.3.39 Chromium: 78.0.3904.108 (Official Build) nightly (32-bit)
I have just updated here and I have updated to 1.3.39. Can you please explain "but no ads"? Thanks
win 10 enterprise ltsc version 1809 32 bit
@riswyre Do you have group policies etc. setup to block Windows native notifications? Do you have Focus Assist enabled?
I've just downloaded dev v1.3.57.
I'll let you know how well it works in the next few days.
After a few hours, I'm seeing no ads. 鈽癸笍
@tmancey ,
Not fixed...
No ads being displayed...
@tmancey ,
Please re-open this ... it's not fixed.
Further testing...
brave when clicked.The desirable behavior is ...
brave to display the ad (opening the application if necessary) ... not working.@tmancey , this isn't fixed.
cc: @Brave-Matt , @GeetaSarvadnya , @jsecretan , @kjozwiak
@rivy I will update you early next, as will discuss internally. Thank you for the above testing and input. Much appreciated. Terry
Added OS/Windows label.
@tmancey , Checking back in ... are you planning to re-open this?
@tmancey Issue is still not fixed. I am not getting any ads when Focus Assist is set to Alarm Only - Ads are not popping up or being displayed under the notification center. Let me know if I am missing anything otherwise, I will log a follow-up issue for it.
As discussed with @tmancey over the slack - there is a change in the behavior as we no longer show ads if notification are not enabled. Also, we won't get any ads when Focus Assist is set to Alarm Only
The detailed test plan is provided in the PR - https://github.com/brave/brave-core/pull/3084
Too bad, that's unfriendly behavior for a lot of early adopters and advocates.
But it's your circus.
Verification passed on
Brave | 1.3.100 Chromium: 79.0.3945.130聽(Official Build)聽beta聽(64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windows聽10 OS Version 1803 (Build 17134.1006)
Focus Assist is set to Alarm Only https://github.com/brave/brave-browser/issues/4102#issuecomment-577847799Clean profile:
[5016:6316:0124/124645.543:INFO:ads_impl.cc(1148)] Notification not made: Notifications not allowed[4428:16072:0124/124905.285:INFO:ads_impl.cc(1305)] Ad notification shown:Upgrade profile:
(Upgrade from 1.2.43 to 1.3.100)
[5652:4820:0124/145717.418:INFO:ads_impl.cc(1148)] Notification not made: Notifications not allowed[9440:11284:0124/150629.389:INFO:ads_impl.cc(1305)] Ad notification shown:Verification passed on
Brave | 1.3.100 Chromium: 79.0.3945.130聽(Official Build)聽beta聽(64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windows聽10 OS Version 1909
Focus Assist is set to Alarm Only https://github.com/brave/brave-browser/issues/4102#issuecomment-577847799
Most helpful comment
@jsecretan should we reprioritize this to maybe a
P3? Seems like we're getting more +1 from Win users who are running into this. Imagine we'll want to get this fixed sooner than later.