Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Currently Xamarin.Forms.Maps has a strict dependency on the specific version of Xamarin.GooglePlayServices.Location v220.127.116.11.
Because of this, I am not able to use in my app Xamarin.GooglePlayServices.Location v18.104.22.168 and other GooglePlayServices assemblies together with Xamarin.Forms.Maps.
Unless there's a strong reason why there Xamarin.Forms.Maps should have a strict dependency on the Xamarin.GooglePlayServices.Location, maybe don't set it?
This has become an issue for us as well. Updated to get firebase which needs v32.
Did you solve you issue Andrei.N, what was you work around
@Roar Using NuGetPackageExplorer I modified the NuGet package to remove the strict dependency.
Definitely not the best thing to do.
It's very disappointing this issue is 5 months old now.
As of 22.214.171.124 when your Android project targets framework 7.0 or greater you may use 126.96.36.199 or greater with Forms Maps. Similar goes for Android Support libraries. Refer to the minimum dependencies that differ from Maps.
This issue shouldn't be closed, there are still issues with Google Play Services..
@Andrei.N please provide more info and a project that demonstrates your issue. We just this morning ran our own Forms project and maps with these dependencies and it works for us.
You're not getting any warnings on the Google Play Services references? Like it's described in the forum post.
@Andrei.N that is correct.
But Matt Ward confirmed the issue and said that owners of Xamarin.Android NuGet are investigating it.
You are saying the opposite, that there's no issue....
@Andrei.N I've reached out to Matt and will make sure I'm in sync with the issue he's seeing/confirming.
What I'm saying is:
a) I am running 188.8.131.52 Forms and 184.108.40.206 Google Play Services and 220.127.116.11 Forms Map
b) I am not receiving any errors or warnings
c) I need more info
Can you (or anyone) please provide a reproduction project that demonstrates this problem?
We have removed maps dependency