-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ads per hour frequency cap incorrectly limits based on adsPerHour not adsPerDay #13215
Labels
bug
OS/Android
Fixes related to Android browser functionality
OS/Desktop
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release/blocking
release-notes/include
Milestone
Comments
moritzhaller
changed the title
Change daycap
Change adsPerHour to adsPerDay in frequency cap
Dec 16, 2020
tmancey
changed the title
Change adsPerHour to adsPerDay in frequency cap
Fix issue with ads per day incorrectly limited to ads per hour
Dec 16, 2020
tmancey
added
bug
feature/ads
priority/P1
A very extremely bad problem. We might push a hotfix for it.
labels
Dec 16, 2020
moritzhaller
added
OS/Android
Fixes related to Android browser functionality
OS/Desktop
OS/iOS
Fixes related to iOS browser functionality
and removed
release-notes/include
labels
Dec 16, 2020
tmancey
added
OS/Android
Fixes related to Android browser functionality
and removed
OS/Android
Fixes related to Android browser functionality
OS/iOS
Fixes related to iOS browser functionality
labels
Dec 16, 2020
moritzhaller
changed the title
Fix issue with ads per day incorrectly limited to ads per hour
Fix issue with adPerHour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Dec 16, 2020
moritzhaller
changed the title
Fix issue with adPerHour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Fix issue with adsPerHour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Dec 16, 2020
23 tasks
moritzhaller
changed the title
Fix issue with adsPerHour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Fix issue with ads per hour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Dec 16, 2020
This was referenced Dec 16, 2020
Merged
moritzhaller
changed the title
Fix issue with ads per hour frequency cap incorrectly limiting based on adsPerHour vs. adsPerDay
Ads per hour frequency cap incorrectly limits based on adsPerHour not adsPerDay
Dec 16, 2020
Verification passed on
Verification passed on Samsung Galaxy J3 version 5.1.1 running
Verified passed on macOS with
Verification passed on
Verification passed on Brave v1.18.74 on Samsung Galaxy Tab S5e (Android 9.0)
|
This was referenced Dec 18, 2020
tmancey
added a commit
to brave/brave-core
that referenced
this issue
Dec 18, 2020
tmancey
added a commit
to brave/brave-core
that referenced
this issue
Dec 19, 2020
Improve Brave Ads unit tests to catch issues such as brave/brave-browser#13215
i mean... id be happy if this remained unresolved. :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
OS/Android
Fixes related to Android browser functionality
OS/Desktop
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release/blocking
release-notes/include
Description
ads frequency cap per hour is using the ads per hour value (5) instead of the ads per day value (20). This bug might result in under delivery of ads.
Steps to Reproduce
Actual result:
ad notification is not delivered due to an incorrect cap which is using ads per hour UI setting
Expected result:
ad notification should be delivered up to the correct cap of 20
Reproduces how often:
easily reproduced
Brave version (info found on brave://version)
introduced in 1.18.x
Version/Channel Information:
Nightly, Beta and Release
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: