-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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] AC SKU doesn't continue retrying if you restart the browser #10243
Comments
just tried it on the latest master (1.12.24) and can't reproduce it. Is this reproducible on 1.11? Maybe just specific to 1.10? |
Reproduced issue from description using
However, did not reproduce the issue using
Steps:
followed shortly by
|
Failed to repro on the latest master. Spoke with @NejcZdovc this morning and we agreed that since the problem is addressed in master and 1.11 is already close to release we can close this out. |
Description
Found by @srirambv
If you are in the middle of AC SKU retries and you close/relaunch the browser, AC doesn't pick up retrying. As a result, your auto contribute never completes.
Steps to Reproduce
--enable-logging=stderr --vmodule=*rewards*=6 --log-level=2 --rewards=staging=true,reconcile-interval=3 --brave-ads-staging
Timer for contribution retry
message (usually 5s). After the second Timer for contribution retry displays in the logs, close the browser. (need to watch closely for this since it is geometric timer and could be seconds or minutes)Actual result:
AC retries don't continue. So the balance is deducted from your Uphold account, but it never displays in the UI as it doesn't finish. If you go to
contribution_info_publishers
table you can see thatcontributed_amount
for second pub listed is 0. This will never get updated after browser restart.Expected result:
AC should continue with retries to finish processing
Reproduces how often:
easily
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc @NejcZdovc @brave/legacy_qa
The text was updated successfully, but these errors were encountered: