Skip to content

"Send a Tip" sometimes not appearing when you've already tipped the same publisher #2272

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

Closed
kjozwiak opened this issue Nov 28, 2018 · 4 comments

Comments

@kjozwiak
Copy link
Member

kjozwiak commented Nov 28, 2018

Description

When tipping the same publisher for the second time, sometimes the Send a Tip disappears and re-appears after a few seconds/minutes. It's pretty variable in terms of when Send a Tip reappears. Sometimes it reappears pretty quickly and sometimes it takes a few minutes.

There's been a few internal reports of this occurring as well. @mandar-brave @bsclifton @LaurenWags @davidtemkin and myself have ran into this in one form or another.

Steps to Reproduce

  1. launch 0.56.15 Chromium: 70.0.3538.110 and enable Rewards via brave://rewards
  2. once enabled, either accept a grant or restore a wallet with some BAT
  3. visit http://clifton.io and send a 5 BAT tip
  4. once the tip has been sent, try tipping again (eventually the Send a Tip area won't appear)

Actual result:

If you've already tipped the same publisher and wanted to do it again, sometimes the Send a Tip area disappears under the Rewards panel. It eventually reappears but varies on how long.

tippingissue

screen shot 2018-11-27 at 6 14 14 pm

Expected result:

The Send a Tip section of the Rewards panel should always be visible.

Reproduces how often:

This issue is about 90% reproducible. Shouldn't be hard to get it into that state.

Brave version (brave://version info)

Brave 0.56.15 Chromium: 70.0.3538.110 (Official Build) (64-bit)
Revision ca97ba107095b2a88cf04f9135463301e685cbb0-refs/branch-heads/3538@{#1094}
OS Mac OS X

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?

Reproduced using the following builds as well:

Brave 0.58.10 Chromium: 71.0.3578.53 (Official Build) dev(64-bit)
Revision 599fb72e740eab9d10609f1ed28a2ad669f82c1a-refs/branch-heads/3578@{#669}
OS Mac OS X
Brave 0.57.8 Chromium: 71.0.3578.53 (Official Build) beta(64-bit)
Revision 599fb72e740eab9d10609f1ed28a2ad669f82c1a-refs/branch-heads/3578@{#669}
OS Mac OS X
@kjozwiak kjozwiak added this to the 1.x Backlog milestone Nov 28, 2018
@mandar-brave mandar-brave added the priority/P3 The next thing for us to work on. It'll ride the trains. label Dec 4, 2018
@NejcZdovc
Copy link
Contributor

@kjozwiak can we retest this on 0.61. I just tried it and can't reproduce

@NejcZdovc NejcZdovc added the needs-investigation A bug not 100% confirmed/fixed label Dec 21, 2018
@eljuno
Copy link

eljuno commented Jan 18, 2019

@kjozwiak
Copy link
Member Author

@kjozwiak can we retest this on 0.61. I just tried it and can't reproduce

I can still reproduce this with the following builds:

Brave 0.59.26 Chromium: 72.0.3626.64 (Official Build) beta(64-bit)
Revision eaa9668e80ce5405e7f1902579558ea725c06ca1-refs/branch-heads/3626@{#708}
OS Mac OS X

Example:

tippingissue

However, I couldn't reproduce this with the following dev build:

Brave 0.60.16 Chromium: 72.0.3626.64 (Official Build) dev(64-bit)
Revision eaa9668e80ce5405e7f1902579558ea725c06ca1-refs/branch-heads/3626@{#708}
OS Mac OS X

Example:

tippingissuedev

@NejcZdovc you'll notice that sometimes the wallet balance is displayed as 0 under the Rewards panel if you try tripping a second time around right after the first tip was sent. I'm assuming this is happening because the first tip didn't get processes yet and Rewards hasn't been updated. It usually gets updates anywhere between 2-3sec to ~1min. When the wallet balance appears as 0 in this situation, you'll get a insufficient funds error when you try tipping even though you have the funds.

It looks like dev tries to complete the first tip before allowing users to tip again right after. Could this be why we're running into issues on beta? You get into a broken state when you try sending tip after tip even though the initial tips haven't beeb processed?

Is the behaviour that I'm seeing on dev expected?

@NejcZdovc
Copy link
Contributor

I notice this 0 as well. Let's close this one as it's fixed on 0.60 and open new one for 0 BAT

@NejcZdovc NejcZdovc modified the milestones: 1.x Backlog, Dupe / Invalid / Not actionable Jan 23, 2019
@NejcZdovc NejcZdovc added closed/not-actionable and removed needs-investigation A bug not 100% confirmed/fixed labels Jan 23, 2019
@kjozwiak kjozwiak removed QA/Yes bug feature/rewards priority/P3 The next thing for us to work on. It'll ride the trains. labels Feb 6, 2019
@rebron rebron removed this from the Dupe / Invalid / Not actionable milestone May 8, 2019
@NejcZdovc NejcZdovc added this to the Dupe / Invalid / Not actionable milestone Jun 3, 2019
@bbondy bbondy removed this from the Dupe / Invalid / Not actionable milestone May 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants