Skip to content
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

Closed
GeetaSarvadnya opened this issue Aug 6, 2020 · 3 comments
Closed

[Desktop] Next payment date is null for a few seconds #11107

GeetaSarvadnya opened this issue Aug 6, 2020 · 3 comments
Assignees

Comments

@GeetaSarvadnya
Copy link

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 the Next payment date is getting reflected in Ads panel

Steps to Reproduce

  1. Clean profile 1.14.121
  2. Enable rewards
  3. Next payment date is null in Ads panel for few seconds

Actual result:

Next payment date is null for a few seconds
image

Expected result:

Next payment date should reflect immediately

Reproduces how often:

80 % Reproducible rate

Brave version (brave://version info)

Brave 1.14.21 Chromium: 84.0.4147.105 (Official Build) nightly (64-bit)
Revision a6b12dfad6663f13a7e16e9a42a6a4975374096b-refs/branch-heads/4147@{#943}
OS Windows 10 OS Version 1903 (Build 18362.959)

Version/Channel Information:

  • Can you reproduce this issue with the current release? No
  • Can you reproduce this issue with the beta channel? Yes
  • Can you reproduce this issue with the nightly channel? Yes

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? NA
  • Does the issue resolve itself when disabling Brave Rewards? NA
  • Is the issue reproducible on the latest version of Chrome? NA

Miscellaneous Information:

cc: @brave/legacy_qa @tmancey

@kjozwiak Confirmed it's working as expected in macOS

@tmancey
Copy link
Contributor

tmancey commented Aug 20, 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

@LaurenWags
Copy link
Member

@tmancey I am ok with that, we can re-visit if it becomes a problem.

any issues with closing this one @GeetaSarvadnya?

cc @kjozwiak

@GeetaSarvadnya
Copy link
Author

Closing the issue as it is reproducible once in 5x attempts.

@tmancey tmancey added this to Ads Jun 10, 2024
@tmancey tmancey moved this to Done in Ads Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

3 participants