Skip to content

No error shown when attaching a file fails #7360

Description

@grzesiek2010

Problem description

When a file picked as an answer can't be read (for example a content://media/... URI pointing at a MediaStore row that another app has left in a pending state) Collect no longer crashes (fixed in #7358), but it doesn't tell the user anything either. The copy silently fails, the question is left unanswered, and from the user's point of view it looks like the pick simply didn't register.

Steps to reproduce the problem

Hard to reproduce on a real device. It needs a file that the system hands over but then refuses to actually read in the original report a download that another app had reserved but never finished writing. Android normally hides files in that state from us, so the usual picker won't give you one. If you do manage to pick such a file, the question stays empty and nothing tells you why.

Expected behavior

Collect should tell the user that the file couldn't be attached, instead of leaving the question empty with no explanation, so it's clear the pick failed and can be tried again with a different file.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions