Crash when Reposting with a 0 LBC Stake and no Channel Selected
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
**DESCRIPTION:**
Attempting to Repost a video with a 0 LBC Stake and no Channel selected results in a Crash.
-----
**REPRO STEPS:**
1) Install and Launch LBRY 0.15.6 on Android 9
2) Navigate to 'Menu > All Content'
3) Select any video
4) Select 'Repost'
5) Select 'Show Advanced'
6) Change 'Deposit' to 0.000
7) Select 'Repost'
**Results:** Crash
**Expected:** Error appears
-----
**ENVIRONMENT:**
- Galaxy S5
- Android 9
- LBRY 0.15.6
-----
**MEDIA:**

-----
**INTERNAL USE:**
-----
**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
-----
**LBRY ADDRESS:**
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
mail@cahlen.org
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash in LBRY 0.15.6 on Android 9 through Menu > All Content > video > Repost > Show Advanced, using a 0.000 deposit with no channel selected. Trace that Repost flow and add or update unit tests so the operation shows an error instead of crashing, then verify the app builds and the listed device scenario passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- blockchain, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100