VS Code running error

[szdenny2]

Is there an existing issue for this?

• I have searched the existing issues
• I have read the guide to filing a bug

Steps to reproduce

Running "flutter pub get" in sly_calculator... 1,030ms
The plugin camera_android doesn't have a main class defined in
C:\Users\test\AppData\Local\Pub\Cache\hosted\pub.flutter-io.cn\camera_android-0.10.8+1\android\src\main\java\io\flutter\plugins\camera\CameraPlugin.java or
C:\Users\test\AppData\Local\Pub\Cache\hosted\pub.flutter-io.cn\camera_android-0.10.8+1\android\src\main\kotlin\io\flutter\plugins\camera\CameraPlugin.kt. This is likely to due
to an incorrect androidPackage: io.flutter.plugins.camera or mainClass entry in the plugin's pubspec.yaml.
If you are the author of this plugin, fix the androidPackage entry or move the main class to any of locations used above. Otherwise, please contact the author of this plugin
and consider using a different plugin in the meanwhile.

Expected results

1

Actual results

1

Code sample

1

Screenshots or Video

1

Logs

1

Flutter Doctor output

Flutter version 3.3.7

[huycozy]

@szdenny2 You are providing output log in Steps to reproduce section.

When opening an issue, please try to provide as much information as possible corresponding to the requested fields, so that we have enough information and confirm the issue.

For quick search results, please see this SO thread that may be helpful: https://stackoverflow.com/questions/71809981/the-plugin-path-provider-android-doesnt-have-a-main-class-defined

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now.
If you find this problem please file a new issue with the same description, what happens, logs and the output of 'flutter doctor -v'. All system setups can be slightly different so it's always better to open new issues and reference the related ones.
Thanks for your contribution.

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