lbryio / lbryio/lbry-android

Unsupported Content Error after Deleting Image from Library

Open
#1,092 0 comments 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

**DESCRIPTION:**

If the user deletes an image from the Downloads page of the Library, they will receive an Unsupported Content error upon trying to view that image again. This appears to be unrecoverable for that image.

-----

**REPRO STEPS:**
1) Install and Launch LBRY 0.16.11 on Android 8.1.0
2) View an image to download it
3) Go to Library > Downloads
4) Delete the image
5) Press the back button to return to image page

**Results:** Unsupported Content error

**Expected:** Page recognizes pre-download state

-----

**ENVIRONMENT:**

- LG V20
- Android 8.1.0
- LBRY 0.16.11

-----

**MEDIA:**

![ErrorImageDelete](https://user-images.githubusercontent.com/30788194/102660288-0a32af80-4138-11eb-8b89-40e23ccbcd12.gif)

-----

**LBRY ADDRESS:**
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
mail@cahlen.org

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

Begin by reproducing the five listed steps on Android 8.1.0, using the supplied LBRY address, and inspect the Library Downloads flow and the image page after deletion. The work is done when returning to the image recognizes its pre-download state instead of showing Unsupported Content.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.