Skip to content
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-enabled metrics is shown in the local state file even after a month of installation/ads enabled #29624

Open
GeetaSarvadnya opened this issue Apr 11, 2023 · 2 comments
Labels

Comments

@GeetaSarvadnya
Copy link

Description

Found while testing #28109
Ads-enabled metrics is shown in the local state file even after a month of installation/ads enabled

Steps to Reproduce

  1. Clean profile 1.51.x
  2. Open brave://local-state file
  3. Ensure that the metrics Brave.Rewards.EnabledInstallationTime not present in the local state file as expected
  4. Enable the rewrads
  5. Reload the brave://local-state file
  6. Ensure that the metrics Brave.Rewards.EnabledInstallationTime response value is 0 as expected
  7. Close the browser
  8. Set the sys date ahead by one month
  9. Relaunch the browser
  10. Reload the brave://local-state file
  11. the metrics Brave.Rewards.EnabledInstallationTime response value is 0 which is NOT as expected as per the test plan step 3 Add support for ephemeral P3A metrics, add ads enabled installation time metric brave-core#16897 (comment)

Actual result:

Ads-enabled metrics is shown in the local state file even after a month of installation/ads enabled

Expected result:

Not sure

Reproduces how often:

Easy

Brave version (brave://version info)

Brave 1.51.79 Chromium: 112.0.5615.49 (Official Build) beta (64-bit)
Revision bd2a7bcb881c11e8cfe3078709382934e3916914-refs/branch-heads/5615@{#936}
OS Windows 10 Version 21H2 (Build 19044.2728)

Version/Channel Information:

  • Can you reproduce this issue with the current release? NA
  • Can you reproduce this issue with the beta channel? Yes
  • Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? NA
  • Does the issue resolve itself when disabling Brave Rewards? NA
  • Is the issue reproducible on the latest version of Chrome? NA

Miscellaneous Information:

cc: @DJAndries @brave/qa-team @mattmcalister

@GeetaSarvadnya
Copy link
Author

The issue is reproducible on Samsung Galaxy version 12 running Bravemonoarm64.apk_1.51.79

@DJAndries
Copy link
Collaborator

@GeetaSarvadnya Did you use a MITM proxy to confirm that the metric was sent before advancing the system time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants