问题
With recent updates to GMS, a new ANR has been introduced. If you exit the app, and then return, that's when the ANR is initialized. The thread trace seems to point to Firebase, but I never even started using Firebase. I guess it must be part of the new GMS package?
06-11 00:34:00.143: E/ActivityManager(1487): ANR in com.myapp
06-11 00:34:00.143: E/ActivityManager(1487): PID: 19700
06-11 00:34:00.143: E/ActivityManager(1487): Reason: Broadcast of Intent { act=com.google.firebase.INSTANCE_ID_EVENT flg=0x14 cmp=com.myapp/com.google.firebase.iid.FirebaseInstanceIdInternalReceiver (has extras) }
Here are my dependencies:
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:design:23.4.0'
compile 'com.android.support:appcompat-v7:23.4.0'
compile 'com.android.support:recyclerview-v7:23.4.0'
compile 'com.google.code.gson:gson:2.4'
compile 'com.mindscapehq.android:raygun4android:2.1.0'
compile 'com.squareup.okhttp:okhttp:2.5.0'
compile 'com.android.support:support-v4:23.4.0'
compile 'com.squareup.picasso:picasso:2.5.2'
compile 'com.google.android.gms:play-services-gcm:9.0.2'
compile 'com.google.android.gms:play-services:9.0.2'
compile 'com.github.chrisbanes:PhotoView:1.2.6'
compile 'com.google.android.gms:play-services-ads:9.0.2'
compile 'com.google.android.gms:play-services-auth:9.0.2'
}
And my emulator has Play Services 9.+
回答1:
To wrap this up, there was a problem in Google Play services 9.6.80. It was fixed in 9.6.83. Likely no one is seeing this problem any more as Play has gone through the 9.8.x release cycle successfully and pretty much all devices should be updated.
来源:https://stackoverflow.com/questions/37760401/firebase-anr-not-even-using-firebase