-
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] Next payment date is null for a few seconds #11107
Labels
Comments
tmancey
added
OS/Android
Fixes related to Android browser functionality
priority/P3
The next thing for us to work on. It'll ride the trains.
release-notes/include
and removed
OS/Windows
labels
Aug 6, 2020
@GeetaSarvadnya @LaurenWags This is due to the time it takes to start the ads service. As the value is populated after the ads service has started I would recommend not fixing |
@tmancey I am ok with that, we can re-visit if it becomes a problem. any issues with closing this one @GeetaSarvadnya? cc @kjozwiak |
Closing the issue as it is reproducible once in 5x attempts. |
GeetaSarvadnya
added
closed/wontfix
and removed
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA/Test-Plan-Specified
QA/Yes
feature/ads
intermittent-issue
priority/P3
The next thing for us to work on. It'll ride the trains.
release-notes/include
labels
Aug 28, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The next payment date is null for a few seconds. As soon as enabling rewards ads panel shows empty
Next payment date
for few seconds after that theNext payment date
is getting reflected in Ads panelSteps to Reproduce
Actual result:
Next payment date is null for a few seconds
Expected result:
Next payment date should reflect immediately
Reproduces how often:
80 % Reproducible rate
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @brave/legacy_qa @tmancey
@kjozwiak Confirmed it's working as expected in macOS
The text was updated successfully, but these errors were encountered: