Skip to content

Document picker error: Error: Warning: previous promise did not settle and you attempted to overwrite it. You've called "pick" while "pick" was already in progress and has not completed yet. #910

Closed as not planned

Description

@bhavesh2706

I have searched open and closed issues for this issue.

  • I have searched open and closed issues.

I have read and understood the license (link below).

  • I have read and understood the license.

Minimal reproducible example

I'm having trouble with Android when I can't choose a file or cancel it at that moment. When I try to open the documents again, I get the error "Document picker error: Error: Warning: previous promise did not settle and you attempted to overwrite it. You've called "pick" while "pick" was already in progress and has not completed yet."

What platform(s) does this occur on?

Android

Did you reproduce on a real device or emulator / simulator?

emulator / simulator

Steps to reproduce

I'm having trouble with Android when I can't choose a file or cancel it at that moment. When I try to open the documents again, I get the error "Document picker error: Error: Warning: previous promise did not settle and you attempted to overwrite it. You've called "pick" while "pick" was already in progress and has not completed yet."

If the issue is related to specific file(s), I have linked the files so that others can reproduce exactly what I see.

  • I have attached files necessary to reproduce the problem (if applicable).

Stacktrace of the crash (if applicable)

No

Your computer environment

Emulator

Activity

  1. CatLover01 commented on Jan 2, 2026

    @CatLover01

    There's an async bug, see here #907
    I'm pushing a PR in the next hour that should fix this

  2. github-actions commented on Jan 2, 2026

    @github-actions
    Contributor

    👋 @bhavesh2706, sorry you're having an issue. As the issue template explains, it's required that you provide a runnable example that reproduces your issue (see the issue template).
    The reason is that a bug report is not actionable without a reproducer. Try to minimize the superfluous code and focus only on reproducing the bug.
    Please create a new issue with this and the maintainer will do his best to review it!.

  3. locked as off topic and limited conversation to collaborators on Jan 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions