Skip to content

Fix incorrect verbose flag in troubleshoot section #12147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Keqy
Copy link

@Keqy Keqy commented Jun 23, 2025

Change -verbose to --verbose in flutter doctor command to match actual CLI behavior

Description of what this PR is changing or adding, and why:
Fixed incorrect flag in the troubleshoot documentation.
The documentation showed "Running flutter doctor –verbose gives..."
but the correct flag is flutter doctor --verbose. This was verified by running flutter doctor --help:
-v, --verbose Noisy logging, including all shell commands executed.
flutter doctor -verbose gives an error:

Could not find an option with short name "-e".
Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

Issues fixed by this PR (if any):
None
PRs or commits this PR depends on (if any):
None

Presubmit checklist

  • This PR is marked as draft with an explanation if not meant to land until a future stable release.
  • This PR doesn’t contain automatically generated corrections (Grammarly or similar).
  • This PR follows the Google Developer Documentation Style Guidelines — for example, it doesn’t use i.e. or e.g., and it avoids I and we (first person).
  • This PR uses semantic line breaks of 80 characters or fewer.

Change -verbose to --verbose in flutter doctor command
to match actual CLI behavior
@Keqy Keqy requested review from sfshaza2, antfitch, parlough and a team as code owners June 23, 2025 18:16
Copy link

google-cla bot commented Jun 23, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@Keqy
Copy link
Author

Keqy commented Jun 23, 2025

I have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant