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

Open
opened 2021-03-11 11:42:12 +01:00 by kekkyojin · 1 comment
kekkyojin commented 2021-03-11 11:42:12 +01:00 (Migrated from github.com)

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
<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. We are also available on live chat at https://chat.lbry.com --> ## 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 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 commented 2021-03-15 15:30:11 +01:00 (Migrated from github.com)

Phone pending should work (or used to), and it should show them a splash screen about pending. Twitter may not, but that would be a bug on the api side which probably doesn't set the is_verified flag.

Phone pending should work (or used to), and it should show them a splash screen about pending. Twitter may not, but that would be a bug on the api side which probably doesn't set the is_verified flag.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
LBRYCommunity/lbry-android#1167
No description provided.