Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Android Google Maps dependency should be "wildcarded" #1
thanks for the plugin! Working well so far.
It seems to be common to use the + wildcard when specifying dependencies in flutter plugins (have a look at all the firebase plugins). This plugin currently hardcodes version 11.0.4:
After changing it to
Thanks for finding this solution, it's interesting to me that the firebase plugin is doing that. Typically in Android you pin your dependencies so your builds are consistent.
I will make this change as well as add some support for checking for a valid Google Play Service version rather than crashing. Would you mind adding the crash logs you were getting to this ticket for some more context. I'm unable to reproduce this on my various devices and emulators currently.
That's the crash log:
I currently use cloud_firestore, firebase_auth, firebase_storage and firebase_messaging plugin, that all rely on some play services / firebase dependencies.
I think the reason for the wildcard usage in firebase plugins is the fact that all plugins can use the same (newest) library version instead of having hardcoded ones that might have different versions as well. To fix that the user would need to "overwrite" the dependency in the apps' build.gradle itself - which is a bit of a hassle if you don't have Android dev experience.