Bug 42976 - Update Xamarin.Forms.Maps to use latest stable release of Xamarin.GooglePlayServices.Location (v29.0.0.2)
Summary: Update Xamarin.Forms.Maps to use latest stable release of Xamarin.GooglePlayS...
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: David Ortinau [MSFT]
Depends on:
Reported: 2016-08-02 07:50 UTC by Andrei.N
Modified: 2017-06-19 21:07 UTC (History)
7 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Andrei.N 2016-08-02 07:50:36 UTC
Currently Xamarin.Forms.Maps has a strict dependency on the specific version of Xamarin.GooglePlayServices.Location v29.0.0.1.

Because of this, I am not able to use in my app Xamarin.GooglePlayServices.Location v29.0.0.2 and other GooglePlayServices assemblies together with Xamarin.Forms.Maps.
Comment 1 Andrei.N 2016-08-10 10:15:08 UTC
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?
Comment 2 Roar Gjøvaag 2016-12-21 14:26:12 UTC
This has become an issue for us as well. Updated to get firebase which needs v32.
Comment 3 Roar Gjøvaag 2017-01-10 10:53:50 UTC
Did you solve you issue Andrei.N, what was you work around
Comment 4 Andrei.N 2017-01-10 10:58:34 UTC
@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.
Comment 5 David Ortinau [MSFT] 2017-03-02 16:04:14 UTC
As of when your Android project targets framework 7.0 or greater you may use or greater with Forms Maps. Similar goes for Android Support libraries. Refer to the minimum dependencies that differ from Maps.
Comment 6 Andrei.N 2017-03-02 16:08:40 UTC
@David Ortinau

This issue shouldn't be closed, there are still issues with Google Play Services..

Comment 7 David Ortinau [MSFT] 2017-03-02 16:16:31 UTC
@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.
Comment 8 Andrei.N 2017-03-02 16:21:01 UTC
@David Ortinau

You're not getting any warnings on the Google Play Services references? Like it's described in the forum post.
Comment 9 David Ortinau [MSFT] 2017-03-02 19:11:52 UTC
@Andrei.N that is correct.
Comment 10 Andrei.N 2017-03-02 20:43:05 UTC
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....
Comment 11 David Ortinau [MSFT] 2017-03-02 22:13:26 UTC
@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 Forms and Google Play Services and 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?
Comment 12 Rui Marinho 2017-06-19 21:07:29 UTC
We have removed maps dependency