-
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
Incorrect response value when ads is enabled after 48 hours but before 72 hours #29653
Labels
Comments
The issue is reproducible on |
GeetaSarvadnya
added
the
OS/Android
Fixes related to Android browser functionality
label
Apr 12, 2023
GeetaSarvadnya
changed the title
Incorrect response value when ads is enabled after 48 hours and before 72 hours
Incorrect response value when ads is enabled after 48 hours but before 72 hours
Apr 12, 2023
Tested with 50 hours and 71 hours, could not reproduce |
@DJAndries: Thanks for checking from your end. Let me retest the issue and post my observations. |
Works as expected hence closing the issue. |
GeetaSarvadnya
added
closed/invalid
and removed
QA/Yes
QA/Test-Plan-Specified
features/P3A
labels
Apr 21, 2023
kjozwiak
removed
OS/Android
Fixes related to Android browser functionality
OS/Desktop
labels
Apr 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Found while testing #28109
Incorrect response value when ads is enabled after 48 hours and before 72 hours
Steps to Reproduce
Brave.Rewards.EnabledInstallationTime
is not shown in the local state fileBrave.Rewards.EnabledInstallationTime
response value is4
instead of3
p3a-json.brave.com
over the network and themetrics_value
is4
instead of3
Actual result:
Incorrect response value when ads is enabled after 48 hours and before 72 hours
p3a-json.brave.com
brave://local-state
Expected result:
Value should be
3
Reproduces how often:
Easy
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @brave/qa-team @DJAndries @mattmcalister
The text was updated successfully, but these errors were encountered: