Errors when running flutter doctor command

[cmee123]

Ok, so I am trying to download flutter and the related apps and set them up. So far I have downloaded the flutter sdk, git, and the android studio. When I run the flutter doctor command I get these errors:

I don't know what any of these problems mean or how to solve them. I have already downloaded the android studio and installed the flutter and dart plugins, but it does not recognize that they are there. I also don't know where the android SDK is, because on android studio it says it is set to a place I can't find in my files. What are these errors, what do they mean, and how do I solve them? I am new to this and don't really know what I am doing, so i may need a little more detail for the solutions.

[hamdikahloun]

Hi @cmee123

Failing to detect the plugins will not affect Flutter development at all. The Flutter CLI tool does not touch the plugins, only your editor does. Because of this, we plan to deprecate the plugin validators : #61246 .

For Powershell warning, Can you try this please #69462 (comment) .

Thank you

[cmee123]

Ok so I think I did that, but it didn’t change anything. I went to the environment variables and then path and pasted it in. I did it on both Variable spots, the user variables and the system variables, because I didn’t know the difference between them. I ran the command again and nothing changed. Also is there anything I need to do about the “unable to locate android sdk” error? Thanks for your help.

[cmee123]

Here are my screenshots:

[cmee123]

Ok so I fixed some of the problems so now when I run the flutter doctor command I get this:

[pedromassangocode]

Hi @cmee123
I would suggest you to try to create and run a Flutter app to see if there is any issue.
As mentioned above sometimes Android Studio does not detect the Flutter plugins but it does not stops you to use Flutter.

I'm closing this for now as this looks like you are looking for assistance.
Thank you

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