Bug 56108 - When will ever Visual Studio compile and include my google-services.json?
Summary: When will ever Visual Studio compile and include my google-services.json?
Status: RESOLVED FIXED
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: N/A
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Jon Dick
URL:
Depends on:
Blocks:
 
Reported: 2017-05-08 19:31 UTC by Magnus Johansson
Modified: 2018-05-15 22:37 UTC (History)
35 users (show)

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


Attachments
Simple project with dummy google-services.json (15.84 KB, application/octet-stream)
2017-06-27 23:47 UTC, Mark McLemore
Details
System info (3.18 KB, text/plain)
2017-06-27 23:51 UTC, Mark McLemore
Details


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:
Status:
RESOLVED FIXED

Description Magnus Johansson 2017-05-08 19:31:35 UTC
After I have added a google-services.json to my project, Visual Studio should use that to include the vital:
		// aapt resource value: 0x7f070049
			public const int gcm_defaultSenderId = 2131165257;
			
			// aapt resource value: 0x7f07004d
			public const int google_api_key = 2131165261;
			
			// aapt resource value: 0x7f07004a
			public const int google_app_id = 2131165258;
			
			// aapt resource value: 0x7f07004e
			public const int google_crash_reporting_api_key = 2131165262;
			
			// aapt resource value: 0x7f07004f

into the Resource.Designer.cs file. Otherwise the Firebase API calls will fail with:
05-06 11:02:55.206: E/FA(4883): GoogleService failed to initialize, status: 10, Missing google app id value from from string resources with name google_app_id. 05-06 11:02:55.212: E/FA(4883): Missing google_app_id. Firebase Analytics disabled. See https://goo.gl/NAOOOI

Now, even if I have set the Build Action to "GoogelServicesJson", it's a once in a blue moon that Visual Studio actually will compile it into my build.
Very fragile and buggy.
Comment 1 Alberto Buratti 2017-05-10 14:22:24 UTC
I found a workaround to this problem, just clean the solution and remove `bin` and `obj` folders. Then recompile it and it works. 
Unfortunately I have to do this every time, otherwise the build fails with the same error.
Comment 2 Albert 2017-05-18 08:48:54 UTC
Hi,

I have exactly the same problem.  It is a pain that I have to "Clean Solution" before building the project.  It is time consuming process.  Please fix the issue. 


Environmnent
Windows 10
VS 2015 14.0.25425.01 Update 3
Xamarin 4.4.0.34
Xamarin.Android 7.2.0.7
Comment 3 Jason Couture 2017-06-14 18:49:22 UTC
Same problem here, very annoying.
Comment 4 Ramy Zbeidy 2017-06-15 05:24:48 UTC
Same here, please fix this
Comment 5 Greg Whatley 2017-06-21 15:57:41 UTC
Would manually adding the required strings (google_api_key, google_app_id, etc.) to Strings.xml be a workaround or would that cause more issues if Visual Studio actually generated them itself?
Comment 6 Mikalai Daronin 2017-06-22 20:22:12 UTC
@ Greg Whatley,
Creating Strings.xml manually (with values from google-services.json) is a workaround.
Comment 7 Jason Couture 2017-06-23 15:57:08 UTC
For the love of god, please fix this.
Comment 8 Mark McLemore 2017-06-27 23:47:25 UTC
Created attachment 23156 [details]
Simple project with dummy google-services.json
Comment 9 Mark McLemore 2017-06-27 23:50:36 UTC
Confirmed -- attached is a simple Xamarin.Android project with a dummy google-services.json (which is included in the project with the GoogleServicesJson build action). Building this project (you may need the workaround in 57816) does not propagate vitals from google-services.json to the resulting app.
Comment 10 Mark McLemore 2017-06-27 23:51:27 UTC
Created attachment 23157 [details]
System info
Comment 11 Ray Kelly 2017-06-28 14:46:35 UTC
Which values need to be copied over to strings.xml for the workaround?  Which mappings from the google-services.json?  

E.g. google_app_id = project_number?
Comment 12 Greg Whatley 2017-06-28 15:01:19 UTC
@ Ray Kelley
These are the ones I used:
(Strings.xml name = path in google-services.json):

gcm_defaultSenderId = project_info.project_number
google_api_key = client.api_key.current_key
google_app_id = client.client_info.mobilesdk_app_id
Comment 13 Lauri Koskela 2017-06-29 11:17:41 UTC
Another workaround is to add the following to the .csproj file:

  <Target Name="RemoveGoogleServicesJsonStampFiles" BeforeTargets="BeforeBuild">
    <Delete Files="$(IntermediateOutputPath)\ProcessGoogleServicesJson.stamp" />
  </Target>

I've had this for a few days now and it seems to work.
Comment 14 joelsc.linder 2017-07-22 10:18:59 UTC
Hi tried #13's solution but it did not help. Is there any other workaround or fix for this bug?
Comment 15 chouthe 2017-07-27 10:04:14 UTC
#13's workaround worked for me.
Comment 16 Jason Couture 2017-07-27 12:40:53 UTC
For the love of God please fix this f***ing issue. It's been 2 almost 3 months now.
Comment 17 Magnus Johansson 2017-07-27 13:03:57 UTC
Haha, @Jason, welcome to the club. 
Expecting anything to be fixed in short term (months) with Xamarin would be a blessing and a miracle. 
I have gotten used to wait years for bugs to be fixed. Like this one (almost 2 years): https://bugzilla.xamarin.com/show_bug.cgi?id=33052

Patience...

/M
Comment 18 Miguel de Icaza [MSFT] 2017-08-18 14:54:27 UTC
Moving this bug to Components, as the bug is with the Google Play Services NuGet package, not Xamarin.Android.

The team has a NuGet package with the fix, which we have not been able to push due to changes on the server that require changes on our CI to work.
Comment 19 Jon Dick 2017-08-18 15:00:20 UTC
There's another temporary work around.

You can replace the file in your solution's:
  packages/Xamarin.GooglePlayServices.Basement.11.0.2/build/Xamarin.GooglePlayServices.Basement.targets

With this one:
https://github.com/xamarin/GooglePlayServicesComponents/blob/11.0.2/basement/buildtasks/Xamarin.GooglePlayServices.Basement.targets

Google Play Services 11.0.4-beta1 packages will be released shortly which contain this fix as well.
Comment 20 Jon Dick 2017-08-21 19:02:42 UTC
If anyone's interested there's some preview packages out that should fix this with version 57.1104.0-beta1
Comment 21 Marcel Wolterbeek 2017-08-25 11:34:33 UTC
After installing the 57.1104.0-beta1 I get:

System.MissingMethodException: Method 'Android.Gms.Common.Zzc.IsGooglePlayServicesAvailable' not found.
Comment 22 James Moore 2017-09-07 19:35:15 UTC
Except that those beta packages mentioned by Jon Dick are broken - https://bugzilla.xamarin.com/show_bug.cgi?id=59265.

This was reported four months ago.  Frustrating.
Comment 23 James Moore 2017-09-08 16:25:36 UTC
This morning's fix to the 57.1104.0-beta1 nugets (59265) has solved this for us.
Comment 24 Andrés González 2017-09-15 16:14:40 UTC
Same problem here, it was working right before I added Microsoft.Azure.Mobile.Push package to my project.


Clean and rebuild solution doesn't worked for me

Please help
Comment 25 James Moore 2017-09-15 16:21:57 UTC
I withdraw my comment about the beta nugets fixing the problem.  We're still seeing it.

The deeply scary thing about this bug is that it means very, very few people are actually using Xamarin for serious Android development.
Comment 26 James Moore 2017-09-15 16:22:39 UTC
Still seeing problem in this release:

=== Visual Studio Professional 2017 for Mac (Preview) ===

Version 7.2 Preview (7.2 build 583)
Installation UUID: 695f9a71-2511-4004-bd9d-d02c38a06e58
Runtime:
	Mono 5.4.0.174 (2017-06/1afb931de69) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 504000174

=== NuGet ===

Version: 4.3.0.4199

=== .NET Core ===

Runtime: Not installed
SDK: Not installed
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin/Sdks

=== Xamarin.Profiler ===

Version: 1.5.6
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 8.3.3 (12175.1)
Build 8E3004b

=== Xamarin.iOS ===

Version: 10.14.0.26 (Visual Studio Professional)
Hash: 416f778f
Branch: d15-4
Build date: 2017-08-25 17:30:05-0400

=== Xamarin.Android ===

Version: 7.5.0.15 (Visual Studio Professional)
Android SDK: /Users/james/androidsdk
	Supported Android versions:
		5.0 (API level 21)
		7.1 (API level 25)
		8.0 (API level 26)

SDK Tools Version: 26.1.0
SDK Platform Tools Version: 26.0.0
SDK Build Tools Version: 26.0.1

Java SDK: /usr
java version "1.8.0_141"
Java(TM) SE Runtime Environment (build 1.8.0_141-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.141-b15, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Inspector ===

Version: 1.3.0
Hash: 8c298a5
Branch: 1.3-release
Build date: Thu, 14 Sep 2017 21:21:26 GMT
Client compatibility: 1

=== Xamarin.Mac ===

Version: 3.8.0.26 (Visual Studio Professional)

=== Build Information ===

Release ID: 702000583
Git revision: 861d3eb8f64655762b85235dde49874645208f51
Build date: 2017-09-05 15:23:48-04
Xamarin addins: 838dc0d12bdbb0407ea44b7bfd11fbe30ddac07b
Build lane: monodevelop-lion-d15-4

=== Operating System ===

Mac OS X 10.12.6
Darwin 16.7.0 Darwin Kernel Version 16.7.0
    Thu Jun 15 17:36:27 PDT 2017
    root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
Comment 27 Jon Dick 2017-09-15 17:10:07 UTC
While we investigate the issue again, please consider using one of the workarounds for now.

You can either add the strings to your resources manually, or invoke the api's which accept the string parameters.

You can find information about what resources are generated from which paths in the json file here: https://developers.google.com/android/guides/google-services-plugin
Comment 28 Jon Dick 2017-09-26 14:59:11 UTC
I believe I've got a fix for this issue.

First of all, our understanding of how resources were handled via Xamarin.Android's build tasks was not quite correct.  I've adjusted the task to build interim versions of the resource files in the `obj/$(Configuration)/procgoogsvcsjson/` folder and add them to the appropriate item group that Xamarin.Android looks at to copy resources to their destination in `obj/$(Configuration)/res/...`.

Next, our resource files that `_GenerateAndroidResourceDir` was copying over for us were still being deleted on incremental builds (they were fine on /t:Rebuild).  

@Dean pointed out to me that when using msbuild (doesn't occur on xbuild), there's a target called `IncrementalClean` that's run which looks for files that shouldn't be in the intermediate output directory.  This for some reason included the files copied over for us.  The fix is to ensure the files we are having copied over end up in the `_CleanCurrentFileWrites` item group so the target leaves them alone.

This commit includes these changes and fixes the behaviour I was able to reproduce that others are seeing for me on Windows in Visual Studio 2017:
https://github.com/xamarin/GooglePlayServicesComponents/commit/36cfb425976dc7c53542b7ff17435b7279d34d68#diff-3c71accc87ca84e8d4d0855b0445ed30R84
Comment 29 xamarinbugzilla 2017-10-17 00:01:57 UTC
Two things - one when will updated nuget with the fix mentioned in #28 be released?
Second - the workaround reported in #13 worked for me as well. What a mess!
Comment 30 Paradise 2017-11-07 19:58:15 UTC
I used #13 solution but my build time is slower than before doing #13.
Please fix this.
Comment 31 Hakan 2017-11-10 12:28:24 UTC
When can we see the fix released?
Comment 32 Paradise 2017-11-11 15:32:46 UTC
please fix this . its 6 months!!!!!!!
Comment 33 Jon Dick 2017-11-13 15:01:11 UTC
This should be fixed in 60.1142.0-beta2.

This release is going through QA process at the moment and will be released to stable soon.  For now, please feel free to use the beta.
Comment 34 Paradise 2017-11-13 22:21:08 UTC
@Jon Dick I tested it but it's not working for google firebase json file.
Comment 35 Mat Gallacher 2017-11-15 10:47:34 UTC
Using the latest beta I get the following issue on VS for Mac

Target _UpdateAndroidResgen:
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018: The "GenerateResourceDesigner" task failed unexpectedly.
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018: System.ArgumentException: Invalid path
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at System.IO.Path.GetDirectoryName (System.String path) [0x000f6] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/Path.cs:240 
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Xamarin.Android.Tasks.GenerateResourceDesigner.AddRename (System.String android, System.String user) [0x00067] in <593a6fd557984367bb21e275d0fa0659>:0 
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Xamarin.Android.Tasks.GenerateResourceDesigner.Execute () [0x001a2] in <593a6fd557984367bb21e275d0fa0659>:0 
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute () [0x00023] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/msbuild-15.4/src/Build/BackEnd/TaskExecutionHost/TaskExecutionHost.cs:631 
    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Microsoft.Build.BackEnd.TaskBuilder+<ExecuteInstantiatedTask>d__26.MoveNext () [0x0022d] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/msbuild-15.4/src/Build/BackEnd/Components/RequestBuilder/TaskBuilder.cs:787 
Done building target "_UpdateAndroidResgen" in project "HomeServe.App.Droid.csproj" -- FAILED.

Done building project "HomeServe.App.Droid.csproj" -- FAILED.

Build FAILED.

/Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(2003,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018: The "GenerateResourceDesigner" task failed unexpectedly.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018: System.ArgumentException: Invalid path
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at System.IO.Path.GetDirectoryName (System.String path) [0x000f6] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/Path.cs:240 
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Xamarin.Android.Tasks.GenerateResourceDesigner.AddRename (System.String android, System.String user) [0x00067] in <593a6fd557984367bb21e275d0fa0659>:0 
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Xamarin.Android.Tasks.GenerateResourceDesigner.Execute () [0x001a2] in <593a6fd557984367bb21e275d0fa0659>:0 
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute () [0x00023] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/msbuild-15.4/src/Build/BackEnd/TaskExecutionHost/TaskExecutionHost.cs:631 
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(1344,2): error MSB4018:   at Microsoft.Build.BackEnd.TaskBuilder+<ExecuteInstantiatedTask>d__26.MoveNext () [0x0022d] in /Users/builder/data/lanes/4992/mono-mac-sdk/external/bockbuild/builds/msbuild-15.4/src/Build/BackEnd/Components/RequestBuilder/TaskBuilder.cs:787
Comment 36 James Moore 2017-11-17 17:51:09 UTC
It's not fixed in this beta version:

=== Visual Studio Professional 2017 for Mac (Preview) ===

Version 7.3 Preview (7.3 build 764)
Installation UUID: 695f9a71-2511-4004-bd9d-d02c38a06e58
Runtime:
	Mono 5.4.1.7 (2017-06/e66d9abbb27) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 504010007

=== NuGet ===

Version: 4.3.1.4445

=== .NET Core ===

Runtime: /usr/local/share/dotnet/dotnet
Runtime Version: 2.0.0
SDK: /usr/local/share/dotnet/sdk/2.0.0/Sdks
SDK Version: 2.0.0
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/4.8.0/lib/mono/msbuild/15.0/bin/Sdks

=== Xamarin.Profiler ===

Version: 1.6.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 9.1 (13532)
Build 9B55

=== Xamarin.iOS ===

Version: 11.4.0.214 (Visual Studio Professional)
Hash: c4240f3f
Branch: d15-5
Build date: 2017-11-08 17:28:18-0500

=== Xamarin.Android ===

Version: 8.1.0.23 (Visual Studio Professional)
Android SDK: /Users/james/androidsdk
	Supported Android versions:
		5.0 (API level 21)
		5.1 (API level 22)
		6.0 (API level 23)
		7.1 (API level 25)
		8.0 (API level 26)

SDK Tools Version: 26.1.1
SDK Platform Tools Version: 26.0.2
SDK Build Tools Version: 27.0.1

Java SDK: /usr
java version "1.8.0_141"
Java(TM) SE Runtime Environment (build 1.8.0_141-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.141-b15, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin.Mac ===

Version: 4.0.0.214 (Visual Studio Professional)

=== Xamarin Inspector ===

Version: 1.4.0-beta1
Hash: 2e30f47
Branch: master
Build date: Tue, 14 Nov 2017 22:32:31 GMT
Client compatibility: 1

=== Build Information ===

Release ID: 703000764
Git revision: 54e0a0247ce488f81f6c7806c9bae93307e66c2b
Build date: 2017-11-08 19:22:55-05
Xamarin addins: 97c21309aa29fd2e7df52a5d7426f39a693ea318
Build lane: monodevelop-lion-d15-5

=== Operating System ===

Mac OS X 10.13.1
Darwin 17.2.0 Darwin Kernel Version 17.2.0
    Fri Sep 29 18:27:05 PDT 2017
    root:xnu-4570.20.62~3/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Internet of Things (IoT) development (Preview) 7.1
Comment 37 Jon Dick 2017-11-17 18:19:38 UTC
We've reworked the build task and targets once more which should hopefully finally resolve this.

Please try 60.1142.0-rc1 which is now on nuget.
Comment 38 Denis 2017-11-18 03:35:32 UTC
I am using v60.1142.0-rc1 (VS 2017, Windows) and have the following errors:


..\packages\Xamarin.GooglePlayServices.Basement.60.1142.0-rc1\build\MonoAndroid80\Xamarin.GooglePlayServices.Basement.targets(66,76): error MSB4064: The "ResPath" parameter is not supported by the "ProcessGoogleServicesJson" task. Verify the parameter exists on the task, and it is a settable public instance property.


..\packages\Xamarin.GooglePlayServices.Basement.60.1142.0-rc1\build\MonoAndroid80\Xamarin.GooglePlayServices.Basement.targets(66,5): error MSB4063: The "ProcessGoogleServicesJson" task could not be initialized with its input parameters.
Comment 39 Jon Dick 2017-11-19 19:46:48 UTC
@Denis

Can you please make sure your VS 2017 is up to date and then try clearing out your bin/ and obj/ folders as well as restarting VS2017.

Your error sounds like something is cached from the old version of the nuget package still (sometimes VS isn't great at loading the new version of the .targets files when you update a package).
Comment 40 Denis 2017-11-20 01:56:08 UTC
Hi Jon, thanks for the quick response.

I updated Visual Studio from 15.4.1 -> 15.4.4 and still had the same issue.

I switched the build log output to detailed and saw something:

1>Building target "ProcessGoogleServicesJson" completely.
1>Output file "obj\Debug\googsvcsjson.stamp" does not exist.
1>Using "ProcessGoogleServicesJson" task from assembly "C:\B2i\B2iDev3\packages\Xamarin.GooglePlayServices.Basement.57.1104.0-beta1\build\MonoAndroid70\Xamarin.GooglePlayServices.Tasks.dll".
1>Task "ProcessGoogleServicesJson"
1>C:\B2i\B2iDev3\AE Mobile\packages\Xamarin.GooglePlayServices.Basement.60.1142.0-rc1\build\MonoAndroid80\Xamarin.GooglePlayServices.Basement.targets(66,76): error MSB4064: The "ResPath" parameter is not supported by the "ProcessGoogleServicesJson" task. Verify the parameter exists on the task, and it is a settable public instance property.
1>C:\B2i\B2iDev3\AE Mobile\packages\Xamarin.GooglePlayServices.Basement.60.1142.0-rc1\build\MonoAndroid80\Xamarin.GooglePlayServices.Basement.targets(66,5): error MSB4063: The "ProcessGoogleServicesJson" task could not be initialized with its input parameters. 

I noticed that whilst every other line in the Build log referenced the new assembly, "one" referenced the old assembly. It turns out my .csproj still had a few superfluous references to the old assembly for some reason. Manually deleting those lines, closing down Visual Studio, deleting the bin and obj contents and then compiling (in that order) has now compiled successfully.

Excellent, now to actually do some development! :)
Comment 41 Mat Gallacher 2017-11-20 11:02:27 UTC
Updated to 60.1142.0-rc1 today and looks like it's working for me!
Comment 42 Mike Gottlieb 2018-05-15 22:37:10 UTC
I'm definitely still seeing this problem right now while trying to upgrade to FCM.

Visual Studio for Mac 7.5.1 (build 22)

Xamarin.GooglePlayServices version 60.1142.1

When was the fixed released?