Bug 46333 - InstanceID.GetInstance crashes because the released GooglePlayServices is ancient
Summary: InstanceID.GetInstance crashes because the released GooglePlayServices is anc...
Alias: None
Product: Android
Classification: Xamarin
Component: Bindings ()
Version: 7.0 (C8)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Atsushi Eno
Depends on:
Reported: 2016-11-02 19:22 UTC by Jeremy Kolb
Modified: 2017-01-05 09:06 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 Jeremy Kolb 2016-11-02 19:22:31 UTC
Crash now occurs with the following line:

var instanceId = InstanceID.GetInstance(this);

The method 'java.io.File android.support.v4.content.ContextCompat.getNoBackupFilesDir(android.content.Context)' was expected to be of type virtual but instead was found to be of type direct (declaration of 'com.google.android.gms.iid.zzd'

This is because you've updated the android support libraries but the Xamarin google play services are many months behind.

See: http://stackoverflow.com/questions/37337393/android-google-cloud-messaging-gcm-token-generation-crash-after-firebase-relat
Comment 1 Jeremy Kolb 2016-11-02 21:38:50 UTC
Moving to GooglePlayServices 32.961.0-beta1 seems to work around this issue.
Comment 2 Atsushi Eno 2017-01-05 09:06:12 UTC
Sounds like the bug was invalid as the component team seemed to have already published GooglePlayServices component at that time.