-
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
[Desktop] Brave Rewards service is associated to Tor Profiles #11223
Comments
This can also be resolved by #11218, however until a decision has been made on how best to resolve we need to fix Brave Rewards |
Closing this issue as #11218 will resolve the issue for all services including BAT Ads and BAT Ledger (Brave Rewards). @LaurenWags If this could still be tested once the above PR lands, that would be great |
Verification passed on Windows 10 x64 using
Clean profile
Once the above was done, created a new
Went through the STR/Cases outlined via #11042 (comment) and ensured that I didn't received random ads from other regions nor two ads at the same time. I went through the case several times and couldn't reproduce. Upgraded profile
Verification passed on
Clean profile
Once the above was done, created a new
Upgraded profile
Verified passed with
Clean profile
Once the above was done, created a new
Went through the STR/Cases outlined via #11042 (comment) and ensured that I didn't received random ads from other regions nor two ads at the same time. I went through the case ~5x and couldn't reproduce. Upgraded profile
Note, I did not encounter #11644 since I upgraded from a version without Rewards.log, however this file could still be available from older versions where logging was enabled. |
Description
Steps to Reproduce
Actual result:
Brave Rewards service is associated to a Tor profile
Expected result:
Brave Rewards service should not be associated to a Tor profile
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: