Skip to content

Add Flutter manifest info to flutter doctor when run from a flutter app directory #37041

Closed

Description

@jmagman

Use case

There are details about an app that would be helpful for triaging certain classes of issues.

Proposal

When people create issues they are instructed to paste the output of flutter doctor -v. When it is run from a directory containing a pubspec.yaml, include the Flutter manifest details:

  • App name
  • Build name
  • Build number
  • Uses material design
  • Uses Anfroid X
  • is module
  • is plugin
  • Android package
  • iOS bundle identifier
  • Supported platforms (if plugin)
    etc.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    t: flutter doctorProblem related to the "flutter doctor" tool
    on Jul 26, 2019
  2. jmagman commented on Jul 26, 2019

    @jmagman
    MemberAuthor

    Related to #36496.

  3. jonahwilliams commented on Jul 26, 2019

    @jonahwilliams
    Contributor

    I think we've backed off the idea of making doctor contextual. One important concern is that the working directory will often not be the project root when it is run via the daemon (vscode, intellij, android studio).

    cc @csells @christopherfujino

  4. jmagman commented on Jul 26, 2019

    @jmagman
    MemberAuthor

    Maybe something explicit?

    flutter doctor -v --project
    

    which just works if you're in the root, or

    flutter doctor -v --project path/to/app
    

    And update the "I have a problem with my Flutter application > Logs" template with instructions. Or the screener can ask for the originator to run it, if they need additional info to triage.

    That output would have been helpful highlighting pubspec parsing issue like #34477.

  5. christopherfujino commented on Jul 29, 2019

    @christopherfujino
    Contributor

    I do like the idea of either making an explicit flag, or perhaps even a new command altogether (though not sure what to call it).

  6. jonahwilliams commented on Jul 29, 2019

    @jonahwilliams
    Contributor

    I don't want to add anymore flags to the doctor command, because it's not obvious how we would surface that in the context of an IDE. We've talked about a flutter check command, or attaching more diagnostics to flutter analyze

  7. jmagman commented on Nov 19, 2019

    @jmagman
    MemberAuthor

    Duplicate of #2885.

  8. github-actions commented on Aug 25, 2021

    @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.

  9. locked as resolved and limited conversation to collaborators on Aug 25, 2021
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

    t: flutter doctorProblem related to the "flutter doctor" tooltoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions