Lbry-desktop: Videos on Explore showing incorrect fee

[42degrees]

Some videos on the Explore page are showing the incorrect fee information. I have LBRY set to be NSFW (I have covered the offending thumbnails).

Here is what I see:

All three of the videos at the bottom of the image initially showed up as "Free" in the Explore page. Clicking into the video showed that the video actually does cost money.

Once it has displayed the correct fee on the video page, it gets displayed properly in the Explore page as well. This happened consistently for all three of these videos.

Acceptance Criteria

1.
2.
3.

Definition of Done

• [ ] Tested against acceptance criteria
• [ ] Tested against the assumptions of the user story
• [ ] The project builds without errors
• [ ] Unit tests are written and passing
• [ ] Tests on devices/browsers listed in the issue have passed
• [ ] QA performed & issues resolved
• [ ] Refactoring completed
• [ ] Any configuration or build changes documented
• [ ] Documentation updated
• [ ] Peer Code Review performed

[tzarebczan]

This is an edge case during a takeover bid and when the user hasn't refreshed their LBRY app in a while. There was a fix applied for the claim page with https://github.com/lbryio/lbry-desktop/issues/797.

I'll keep this open, but the more generic issue to tackle might be: https://github.com/lbryio/lbry-desktop/issues/451

[kauffj]

Hey @42degrees, just wanted to say thanks for some of the thorough, well-written issues you've filed as well as your first contrib. I'm guessing @tzarebczan has already hooked you up with some LBC, so this is just a thank you from me and the rest of the LBRY team!

[42degrees]

@kauffj Thanks for the compliment. @tzarebczan has indeed been throwing shekels my way ;-)

[42degrees]

@tzarebczan I had just upgraded to the new beta of LBRY, so I had definitely refreshed my LBRY immediately before seeing this error (within 5 minutes at most). And that release had a new daemon as well, so that was brand new when I saw this problem. Certainly it seems like it could have just been bad timing, but that sounds like a transactional problem, if so.

[tzarebczan]

We'll see if we can get the same fix applied from https://github.com/lbryio/lbry-desktop/pull/1563 to other areas, or remove this cost-refresh dependency completely.

[tzarebczan]

This should now be fixed.