Bug 42576 - Attribution text returned from Google Play Services map component is null
Summary: Attribution text returned from Google Play Services map component is null
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jon Dick
Depends on:
Reported: 2016-07-15 00:23 UTC by michael
Modified: 2017-09-28 15:25 UTC (History)
1 user (show)

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 michael 2016-07-15 00:23:47 UTC
There's a legal requirement to display the attribution text when using Google maps within the app, however the text returned by the method to retrieve the text (GoogleApiAvailability.Instance.GetOpenSourceSoftwareLicenseInfo(...)) is null.

Happens when using the Google Play Services component or nuget packages. There seems to be an issue raised with Google about this as well (https://code.google.com/p/gmaps-api-issues/issues/detail?id=9813) but not sure if there are also changes required for the Xamarin bindings
Comment 1 Bill Holmes 2016-07-15 14:41:57 UTC
As mentioned above this appears to be a Google issue and we need to wait for them to resolve it.

However I have assigned to Jon to be sure.
Comment 2 Jon Dick 2017-09-28 15:25:11 UTC
This works fine on newer versions of Google Play Services.