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

Clicking solve on adaptive captcha notification doesn't show captcha if auto-contribute disabled #21311

Closed
emerick opened this issue Feb 25, 2022 · 5 comments · Fixed by brave/brave-core#12409

Comments

@emerick
Copy link
Contributor

emerick commented Feb 25, 2022

Description

Users with auto-contribute disabled in Rewards are not able to complete scheduled adaptive captchas.

Steps to Reproduce

  1. Schedule an adaptive captcha for a particular wallet id
  2. Have that user enable Rewards, disable auto-contribute, and restart the browser
  3. Exhaust unblinded tokens by viewing/rating ads
  4. Eventually, notification will appear for scheduled captcha
  5. Click Solve on the notification

Actual result:

Nothing happens. Rewards panel doesn't open and captcha doesn't appear.

Expected result:

Rewards panel should open and display the captcha to solve.

Reproduces how often:

Easily

Brave version (brave://version info)

Current nightly

Version/Channel Information:

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

Other Additional Information:

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

Miscellaneous Information:

@emerick emerick added feature/rewards priority/P2 A bad problem. We might uplift this to the next planned release. QA/Yes release-notes/include OS/Desktop labels Feb 25, 2022
@emerick emerick self-assigned this Feb 25, 2022
@emerick
Copy link
Contributor Author

emerick commented Feb 25, 2022

cc: @gpestana @Miyayes

@kjozwiak
Copy link
Member

Will require 1.36.107 or higher.

@LaurenWags
Copy link
Member

LaurenWags commented Feb 28, 2022

Verified with

Brave | 1.36.107 Chromium: 99.0.4844.45 (Official Build) (x86_64)
-- | --
Revision | edbc0b8343c7b10fddb0e1b4efb280b0f6e38cab-refs/branch-heads/4844@{#788}
OS | macOS Version 12.2.1 (Build 21D62)

Verification notes can be found under https://github.com/brave/internal/issues/857#issuecomment-1054299509

@kjozwiak
Copy link
Member

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.36.107 Chromium: 99.0.4844.45 (Official Build) (64-bit)
-- | --
Revision | edbc0b8343c7b10fddb0e1b4efb280b0f6e38cab-refs/branch-heads/4844@{#788}
OS | Windows 11 Version 21H2 (Build 22000.527)

Verification notes can be found via https://github.com/brave/internal/issues/857#issuecomment-1054680063.

@btlechowski
Copy link

Verification passed on

Brave 1.36.109 Chromium: 99.0.4844.51 (Official Build) (64-bit)
Revision d537ec02474b5afe23684e7963d538896c63ac77-refs/branch-heads/4844@{#875}
OS Ubuntu 18.04 LTS

Verified in https://github.com/brave/internal/issues/857

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment