lbryio / lbryio/lbry-android

Allow manual wallet unlocking and prompt/saving of password

Open
#635 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

hacktoberfest help wanted type: new feature
Dominant language
Java
Stars
2.4k
Forks
110
PR merge metrics
No merged PRs in 30d

Description

## The Issue
If an incorrect password is provided to account unlock/sync apply, or if the wallet is locked, the app should prompt the user for their password. It should save this value like it does when setting it up initially.

Scenarios:
1) Some users have run into a bug where the wallet is locked and they can't stream/send any funds. They have to uninstall/reinstall.

2) If the wallet sync password changes, the user should be prompted for the new one.

## Anything Else

## Screenshots

## 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

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

Start by tracing the account unlock and sync-apply flows, then inspect how the wallet handles a locked state and how the initial password is saved. Reproduce both an incorrect or changed sync password and a locked wallet. Done means the app prompts for the password, saves the accepted value, and allows the affected wallet actions without reinstalling.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
authentication, mobile, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.