-
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
Rewards: "Next Contribution Date" Sometimes displays a past date #2206
Comments
problem with this one is probably that timers that we use are not checking if past and they don't reset it to next month or trigger contribution |
For what it's worth, I seem to have hit this as well, on v0.56.15. |
I'm having the same problem. Just updated to v0.57.18 and it still doesn't seem to trigger contributions. |
More info: I still have this in 0.57.18, and right upon updating to 0.57.18 on Friday (Dec. 7th, 2018), I got the message "Your contribution did not go through due to insufficient funds". (I definitely have enough funds to cover my contribution since I have over 100 BAT.) Not sure whether this is related to the strange state of my wallet (of which this issue is a symptom), or if it was just a quirk upon updating. |
I'm still hitting this on v0.57.18 (mac). |
My contribution date is stuck in the past as well on Dev
Also, looks like I'm getting a message about insufficient funds but I do have more than enough: |
Verification passed on
Verification passed on
Used test plan from brave/brave-core#1168 Verified passed with
|
@DivineOmega if you go to chrome://rewards-internals/ do you have any contributions in progress? |
@NejcZdovc I see the following. I've redacted the IDs as I'm not sure if there are privacy implications of revealing them publicly.
|
@DivineOmega this is what I though. So your contribution is in retry flow. After retry will be done (successfully or not) contribution date will be moved. Do you have enough funds to complete this transaction? We can improve UI in this regard and say something like (in progress or retrying) |
@NejcZdovc I do have sufficient funds in place (5.1 BAT, earned from ads). To try to get this working, I removed all pending contributions and restarted the browser. I then received a message stating there was an error processing my contribution. The rewards-internal page still shows a contribution in progress. However, the next contribution date has correctly advanced to the next month (28 Sep). |
@DivineOmega money earned from rewards is (behind the scenes) treated differently than money you have deposited yourself. @NejcZdovc is there a problem here where the balance from advertising grant is not considered? |
@bsclifton I think the problem is that @DivineOmega had some recurring tips set up. And we combine AC and recurring tips and check against balance as one. So for example if you have 5 BAT AC and 3 publishers with 1 BAT recurring you need 8 BAT to process it. It's all or nothing approach. |
@NejcZdovc @bsclifton I'm afraid I've not made use of the tips system at all yet, recurring or otherwise. I'm only using the automatic contributions. |
Oh ok, sorry I misread it then. Will try couple of things to reproduce it |
I'm getting this issue also on the latest Brave Android version, but have no retry attempt listed in chrome://rewards-internals/ |
Description
In
Rewards Settings --> Auto-Contribute
, the "Next Contribution Date" sometimes displays dates that are in the past:Above picture courtesy of @Miyayes
Below picture from Community user (oddly enough it displays the same date, not sure if relevant)
Steps to Reproduce
No STR as far as I know. cc @Miyayes for additional info.
Note: This issue occured before the update today to v0.56.14
Actual result:
(See image in Description)
Expected result:
Next Contribution Date should display a valid (and accurate) date.
Reproduces how often:
Unclear/No STR
Brave version (brave://version info)
Release build v0.55.12
Reproducible on current release:
Unclear
Additional Information
Link to Community user encountering the issue:
https://community.brave.com/t/2-brave-rewards-payments-bugs/37847
The text was updated successfully, but these errors were encountered: