You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add Flutter manifest info to flutter doctor when run from a flutter app directory #37041
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:
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).
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.
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
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.
Activity
jmagman commentedon Jul 26, 2019
Related to #36496.
jonahwilliams commentedon Jul 26, 2019
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
jmagman commentedon Jul 26, 2019
Maybe something explicit?
which just works if you're in the root, or
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.
christopherfujino commentedon Jul 29, 2019
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).
jonahwilliams commentedon Jul 29, 2019
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 checkcommand, or attaching more diagnostics toflutter analyzejmagman commentedon Nov 19, 2019
Duplicate of #2885.
github-actions commentedon Aug 25, 2021
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 -vand a minimal reproduction of the issue.