-
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
ads staging flag uses brave.com
domain
#24574
Comments
Reproduced on macOS using:
Launched with: But am seeing calls to brave.com:
|
Verification passed on
Verified test plan from the description stagingissuers
catalog
subdivision
refill
signed tokens
redeem
create confirmation
fetch payment token
redeem unblinded payment tokents
productionissuers
subdivision
catalog
refill
signed tokens
redeem unblinded token
create confirmation
FetchPaymentToken
RedeemUnblindedPaymentTokens
|
ads staging flag uses
brave.com
instead ofbravesoftware.com
. Ads staging env is broken.Regression introduced in 1.44.x. Not reproducible in 1.43.x
Steps to Reproduce
--rewards=staging=true
Actual result:
ads requests are made to
brave.com
Expected result:
ads requests are made to
bravesoftware.com
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
cc @jsecretan @tmancey @rebron @brave/qa-team
The text was updated successfully, but these errors were encountered: