-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Don't know what is this issue exactly #29
Comments
Hi @aTeamSolace , I think the package Please update to version 0.9.4 and check if it is working as I updated geolocator's version to newest one in that version. FYI, both google_api_availability and geolocator are 3rd party packages which means we are limited to handle issues related to it. |
hi @fysoul17, I updated version to 0.9.4 but still, this issue occurred. I also use flutter clean command and then flutter package get but still occurring. |
Have you tried with an empty project? |
no not with an empty project |
In the meantime, try to remove 'pubspec.lock' file and rebuild to see if it still happens. |
no sir, |
Yes, it is because that plugin also uses I am sorry but I have no idea of what is happening there. |
Closing as there is no further update. |
The plugin
google_api_availability
doesn't have a main class defined in E:\flutter_installation\flutter.pub-cache\hosted\pub.dartlang.org\google_api_availability-2.0.4\android\src\main\java\com\baseflow\googleapiavailability\GoogleApiAvailabilityPlugin.java or E:\flutter_installation\flutter.pub-cache\hosted\pub.dartlang.org\google_api_availability-2.0.4\android\src\main\kotlin\com\baseflow\googleapiavailability\GoogleApiAvailabilityPlugin.kt. This is likely to due to an incorrectandroidPackage: com.baseflow.googleapiavailability
ormainClass
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.The text was updated successfully, but these errors were encountered: