Skip to content

[tool_crash] Invalid argument(s): Cannot find executable for /flutter/bin/cache/artifacts/ #52499

Closed as not planned

Description

@christopherfujino

TL;DR Workaround

Wiping out the flutter cache will cause the flutter tool to re-try downloading the required cached artifacts when next invoked, which will usually fix the issue.

$ rm -rf <path to flutter installation>/bin/cache
$ flutter run -v# or whatever command you were attempting

Issue

The current caching mechanism in the tool does not guarantee that a cached binary is present before invoking.

Proposed solution

Rather than directly invoking a binary from the flutter cache using processutils, we should have a method on the cache that first checks for the file's existence, and if it isn't there tries to download it first, then invoke.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Mar 12, 2020
  2. added this to the April 2020 milestone on Mar 12, 2020
  3. changed the title [-]Implement process call wrapper methods for cache artifacts that ensures existence[/-] [+][tool_crash] Invalid argument(s): Cannot find executable for /flutter/bin/cache/artifacts/[/+] on Apr 8, 2020
  4. modified the milestones: April 2020, on May 5, 2020
  5. modified the milestones: , on May 5, 2020
  6. added
    P2Important issues not at the top of the work list
    on May 29, 2020
  7. modified the milestones: , 1.23 - September 2020 on Jun 18, 2020
  8. modified the milestones: 1.23 - September 2020, on Oct 6, 2020
  9. removed this from the milestone on Oct 6, 2020
  10. removed their assignment
    on Oct 6, 2020
  11. github-actions commented on Jul 11, 2025

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  12. locked as resolved and limited conversation to collaborators on Jul 11, 2025
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

    P2Important issues not at the top of the work listc: crashStack traces logged to the consoleteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions