-
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
P3A - Ads response value isn't updated correctly in upgraded profile #7253
Comments
I waited 20+ minutes and this question - Q17, didn't appear in my upgraded profile. It seemed like questions were slowly being added to my upgraded local-state file. I eventually got up to 14 questions and then they seemed to stop appearing in local-state. After following the STR in description, upgrading, and waiting the 20 minutes, I toggled Ads on and off again in brave://rewards and then the question displayed in local-state. When I did this I got the expected value of |
@LaurenWags There is a change in your STR.
I haven't performed this step in the original issue. I have enabled wallet and disabled ads in 1.0.1. After upgrade to 1.1.18, it should have recorded the value as 1 instead of 0 |
@GeetaSarvadnya I added that step bc after waiting 20+ minutes the question never appeared on my upgraded profile 😞 |
@LaurenWags should be fixed here brave/brave-core#3931 |
Verification passed on
Verified passed with
Verification passed on
|
Description
Found while testing #6285
Ads response value isn't updated correctly in an upgraded profile. Found while testing Q17
Q17: Have you enabled Brave Ads?
(Brave.Rewards.AdsState)
Steps to Reproduce
0
instead of1
Actual result:
Ads response value isn't updated correctly in upgraded profile
Expected result:
Ads response value should be updated correctly in upgraded profile
Reproduces how often:
Always
Brave version (brave://version info)
1.1.18
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @brave/legacy_qa @iefremov @bsclifton @rebron
The text was updated successfully, but these errors were encountered: