Bug 60635 - Failed to register Google Play Account. Google.Apis.Json.NewtonsoftJsonSerializer throw an exception
Summary: Failed to register Google Play Account. Google.Apis.Json.NewtonsoftJsonSerial...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-11-13 04:15 UTC by Deyun Liu
Modified: 2017-11-14 01:03 UTC (History)
5 users (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 for Bug 60635 on Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:

Description Deyun Liu 2017-11-13 04:15:26 UTC
My customer is having an issue after updating Xamarin in Visual Studio 2015.

He mentioned one forum question where he has posted his problem there also:


I have checked with customer that he confirmed his Newtonsoft.Json library is added into every project and version is 10.0.3 which should be correct.

And this only happened after updating 2 stable versions of Xamarin according to customer.

Now he is having issue publishing his new version of the application. Can you help to check on this whether this is a bug or known issue? Or is there any workaround regarding this issue?
Comment 1 Jon Douglas [MSFT] 2017-11-14 01:03:04 UTC

Can you please follow our bugzilla writing guide and provide us more information on this issue?


For example, we will want to know the exact version information that is being used, and a way that we can reproduce this.

Some other questions might include: Does this happen on Visual Studio 2017 or Visual Studio for Mac? Is this only isolated to Visual Studio 2015? 

In all, please provide:

1. Steps to reproduce
2. Actual Results
3. Expected Results
4. Version Information

Changing Product to Visual Studio for more visibility.

Thanks for reporting a bug!