lbryio / lbryio/lbry-android

User is offered to be verified while its status is in Reward Approval Pending

Open
#1,167 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
2.4k
Forks
110
PR merge metrics
No merged PRs in 30d

Description

The Issue

Steps to reproduce
  1. Verify email address
  2. Verify account with Twitter or Phone Number
  3. Open Rewards activity
Expected behaviour

User should be informed its account is pending approval for rewards

Actual behaviour

User sees the same page as it is net yet been verified, allowing it to "Get Started" -verify wil Twitter, Phone Number or paying the fee- or go back.

This is both confusing for user who has yet ben verified and resource consuming for LBRY, as more verification requests would be performed to its servers because of user's confussion.

Internal Use

Acceptance Criteria
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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the listed email, Twitter or phone verification steps, then trace the Rewards activity flow for the Reward Approval Pending status; done means pending users see an approval-pending message instead of the verification prompt, with the project building and relevant tests passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.