a-c table not being updated correctly
See original GitHub issueDescription
Updating from 0.58.18 to 0.58.20 appears to keep the Auto Contribute table intact. However, once you start visiting sites, you’ll notice that the a-c table isn’t being updated properly. For example, the first site you visit which meets criteria to be added to the table (regardless of whether it was already in the table previously), is listed at 100%. If you visit a site that was already in the table, you will see two listings for that site. It seems like your already existing sites (prior to update) don’t appear to be taken into account - it’s like you started with a completely clean table.
Steps to Reproduce
- Have a profile with rewards data from 0.58.18.
- Update to 0.58.20 (I can only update on
test
channel, so I swapped the .app files on mac) - Launch 0.58.20 and open brave://rewards page. You will see that your a-c table looks intact.
- Visit a site that isn’t already in the table so that it meets minimum criteria.
- Go back to brave://rewards.
- Site is listed first at 100% and already existing sites remain displayed in table
Actual result:
When you continue to visit sites, some already in table and some not, you will see that your % values don’t add up. Your already existing sites (prior to update) don’t appear to be taken into account - it’s like you started with a completely clean table. Below I visited a site which was already in the table. You’ll see that it gets added a second time:
Expected result:
Existing sites should not be ignored and should be taken into account for table entries and % values
Reproduces how often:
easily
Brave version (brave://version info)
Brave | 0.58.20 Chromium: 71.0.3578.98 (Official Build) (64-bit) |
---|---|
Revision | 15234034d19b85dcd9a03b164ae89d04145d8368-refs/branch-heads/3578@{#897} |
OS | Mac OS X |
Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds?
Website problems only:
- Does the issue resolve itself when disabling Brave Shields?
- Is the issue reproducible on the latest version of Chrome?
Additional Information
cc @brave/legacy_qa for verification on other platforms cc @rebron @NejcZdovc @mandar-brave
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top GitHub Comments
@GeetaSarvadnya steps looks good to me
Verified the issue on Windows 10 x64 - Followed below steps
Publisher_info_db:
@NejcZdovc Can you verify the steps and let me know is this the correct way to test this defect. @LaurenWags can you please verify steps and let me know if i have missed anything.