-
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
Only make requests to *.rewards.brave.com endpoints after Rewards opt-in #14277
Comments
There should only be a few more remaining cases (that we know of) for this:
The verification check can be deferred until user is opted in Status TBD on Android (@deeppandya can you help verify?). All other cases have been closed (ex: with brave/brave-core#8036). Nice work @zenparsing @emerick 😄 |
Given above - going to reprioritize this issue based on the remaining two cases |
Is there a way to reset Brave Rewards status? I enabled it once but have since tried to disable it as much as possible - including turning off ads, hiding the rewards button, and resetting the wallet. However, I can't get back to the state where it says, "Start using Brave Rewards" without creating a new profile. Using my old profile, I still get calls to *.rewards.brave.com endpoints. |
@holow29 I gave this a shot on a profile which had rewards enabled and here's what I found:
I don't know if we've ever characterized a way to "reset" this once opt-in is done. Will need to investigate more cc: @brave/rewards-client |
Potentially some more info: I restarted the browser and Utility: Bat Ledger Service was not running, and I didn't see any calls to *.rewards.brave.com endpoints. However, when I went to brave://rewards to ensure everything was off, the ledger service started again and remained running. |
Thanks for testing! I raised issue today to @Miyayes - we can figure out next steps 😄 But as long as you quit the browser and re-open (as long as no brave://rewards windows are open), it won't be running Ledger There is a possibility Ads service might run, if you enable Brave News. That's something to keep in mind. Even if you turn off Brave news, it'll still be running (that bug is captured by #17491) |
From latest look into this, it looks like Rewards endpoints and URLs are hit when a not opted-in user:
@diracdeltas In your view, is this acceptable, or should Rewards endpoints only ever be hit once the user opts in to Brave Rewards (as in, goes to generate a Brave Rewards wallet)? cc: @evq |
@Miyayes thanks for the info! i will mostly defer this to @PrivacyMatters but i think we shouldn't be adding more of these. for instance it seems this has slightly regressed since #14277 (comment) (now navigating to brave://rewards triggers a request) |
Verified with
Reproduced the issue using 1.44.112
Logs
Logs
Logs
Logs
Logs
Verified test cases from #14277 (comment). Case 1 - Greaselion - PASSED
Case 2 - BAT icon - PASSED
Case 3 - brave://rewards page - PASSED
Case 4 - In-line tip button - FAILED, follow up issue logged
Logged #26109 for case 4. |
Verified on
Test Plan #14277 (comment). Case: BAT icon - PASSED
Case: brave://rewards page - PASSED
Case: In-line tip button - PASSED
|
@Miyayes apologies for the delay. re #14277 (comment) yes, it is acceptable |
Thanks. @PrivacyMatters In any case, we actually went for the stronger route, and we make no calls to rewards-related endpoints until the user explicitly opts in/enables Brave Rewards :). |
Description
Browser sometimes makes calls out to
*.rewards.brave.com
endpoints before user fully opts into Brave Rewards. For example, see brave/brave-site-specific-scripts#41. Any*.rewards.brave.com
requests should only occur if the user has pressed "Start using Brave Rewards" and generated a wallet. These calls can happen as a result of Greaselion or by clicking the BAT icon.Requests are made to the following domains, for example:
api.rewards.brave.com
rewards.brave.com
grant.rewards.brave.com
Steps to Reproduce
Greaselion
*.rewards.brave.com
Another way:
BAT icon
*.rewards.brave.com
Calls should be deferred until after the user has pressed "Start using Brave Rewards".
Expected result:
No requests needed until after opt-in.
Task list
The text was updated successfully, but these errors were encountered: