Forum Xamarin.Android
We are excited to announce that the Xamarin Forums are moving to the new Microsoft Q&A experience. Q&A is the home for technical questions and answers at across all products at Microsoft now including Xamarin!

We encourage you to head over to Microsoft Q&A for .NET for posting new questions and get involved today.

GCM Push notifications no longer working since updating Google SDK libraries and Xamarin/Google pkgs

DennisLeeDennisLee USMember ✭✭
edited January 2017 in Xamarin.Android

Since doing an update of Google and Xamarin libraries and packages, push notifications no longer work via GCM.

We are running into the same issue that is identified here:

var instanceId = InstanceID.GetInstance(Application.Context);

throws the exception:

Exception: "The method '' was expected to be of type virtual but instead was found to be of type direct (declaration of 'java.lang.reflect.ArtMethod' appears in /system/framework/core-libart.jar)
The method '' was expected to be of type virtual but instead was found to be of type direct (declaration of 'java.lang.reflect.ArtMethod' appears in /system/framework/core-libart.jar)"

Has anybody else run into this and fixed this issue or come across a workaround? This is a critical issue for us, as our current production release is broken.



  • EstevexEstevex USMember

    Hi @DennisLee

    I am also having that issue just now.
    Have you found a solution?

    I am going to try a few stuff and if I find something I will update this thread.


  • JonDouglasJonDouglas USXamarin Team, University, Developer Group Leader Xamurai

    Hello there,

    Can you both please provide what versions of Xamarin and Google libraries you updated FROM -> TO?

    If any of you have a sample application, this can also help us investigate the issue further.

    Thank you!

  • DennisLeeDennisLee USMember ✭✭

    I was able to get past that problem thanks to Ming (
    There were a couple of problems, one, Google changed the location of some classes in their Google Play Services in the Jan/Feb updates. Second, updating the corresponding version of Xamarin plugins didn't seem to work correctly, and I had to remove the packages folder and restore and fix the references.

Sign In or Register to comment.