-
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
browser doesn't retry to get signed tokens in all cases #6647
Labels
bug
feature/ads
priority/P3
The next thing for us to work on. It'll ride the trains.
QA/No
QA Pass-macOS
release-notes/include
Milestone
Comments
jsecretan
added
the
priority/P3
The next thing for us to work on. It'll ride the trains.
label
Nov 21, 2019
32 tasks
|
Waiting on @tmancey to add some info re: reproducing the |
This was referenced Feb 4, 2020
Due to this being hard to QA and which takes up a lot of time, we're going to check a single platform to make sure it's working after speaking with both @tmancey and @jsecretan. |
Verification PASSED on
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/ads
priority/P3
The next thing for us to work on. It'll ride the trains.
QA/No
QA Pass-macOS
release-notes/include
Description
While testing I got a
Tokens don't exist
response from the server on several profiles. When this occurred, the browser did not retry to get signed tokens again. Because of this, I was not served Ads.Steps to Reproduce
--enable-logging=stderr --vmodule=brave_ads=3 --log-level=2
Actual result:
Rarely, you might encounter below message. Afterwards, the browser does not retry to get signed tokens, so Ads are not served to the user.
If you keep watching, there are no retry attempts.
Expected result:
When error above is encountered (as it is a legitimate error), the browser should retry to get signed tokens.
Reproduces how often:
Getting the
[16257:775:1029/100755.041890:INFO:refill_tokens.cc(183)] Response: {"error":"Tokens don't exist","statusCode":404}
is rare, but once you get the message, it is easy to see that the browser does not retry.Brave version (brave://version info)
encountered with
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @tmancey @jsecretan @brave/legacy_qa
The text was updated successfully, but these errors were encountered: