New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ANR #594
Comments
@LiuDongCai this is not enough information to debug. Are you getting this from Crashlytics or something? Is this a new issue? If so, does it correspond to an SDK update? |
@samtstern This is anr in Google play. It just happen at Android 8.0. |
@LiuDongCai while I do believe this is a real issue for you, it's not possible to begin fixing it unless we can reproduce the issue as well. See this page for more information on how to file an actionable bug report: |
You are literally the 4th result on the first page of search results for "Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 ANR". It would be good of you to take on a bit of responsibility and investigate. If you read the news group thread at search result 3 it looks like Vitalii may have already debugged it for you. https://groups.google.com/d/msg/firebase-talk/5mo7-z8gqFA/RugthckUCgAJ. I cannot overstate my disappointment with such apathy. |
@nmr8acme sorry that you're disappointed. It certainly wasn't "apathy" that led me to close this issue, it was a lack of the information we need to debug the issue. A copy-pasted dump from a crash report just isn't enough. Your link to the google groups post (which I hadn't seen before) contains much more information and is very helpful! I will use this to file a more detailed bug report with the authors of the InstanceID SDK and see if they can fix it. Looking at the source for |
Requiring a repro is a rather high bar to set for what looks like a tricky bug. Thank you for pursuing it. FWIW I am experiencing this bug on firebase-iid 16.0.0. I'll try updating, which, to complain more, would be substantially easier if InstanceIDListenerService hadn't been deprecated. |
Here are some initial thoughts I got from the engineer who wrote the code involved here (slightly paraphrased to remove internal terminology). It seems that we're aware of the general issue and we're using a number of techniques to try and avoid this, but there are still cases where the broadcast doesn't finish fast enough and we see ANRs. We are continuing to investigate. An FCM message broadcast comes in via the If the app is running on a device <O or is targeting <O we just use [...] For normal priority messages, we keep the broadcast going (via The [recent changes mean] that for high priority messages, where [the system gives] the app a short whitelist that allows them to take wake locks, hit the network, start services, etc. we use This is much more important here as for high priority messages we use a foreground broadcast that triggers an ANR in the receiver after 10s (which is why we set the timeout to 9s) - but worse than that can cause system issues as foreground broadcasts are expected to be fast. Even with that change though I still hear some reports of ANRs, which I haven't been able to diagnose. |
@nmr8acme our reccomendations right now:
|
Great advice, thanks. Part of what makes this a tough bug is that the stack traces in the ANR tombstones are "empty", i.e. main thread is not blocked, just sitting there in the looper, which is a bit baffling.
|
We had the same ANR issue |
same thing to me Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 pkg=com.tencent.qqlivei18n cmp=com.tencent.qqlivei18n/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) } "main" prio=5 tid=1 Native |
@samtstern i have some operations that could take more than 10 seconds but i use AsyncTask to execute those operations even i tried with WorkManager and the result is the same i got a lot of ARNs Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000010pkg=schan.main cmp=schan.main/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) ### }, VisibleToUsercom.google.firebase.iid.FirebaseInstanceIdReceiver
|
"main" tid=1 Native |
I am also facing this issue. 95% of the ANRs that are getting reported on my Google Play Console are referring to this issue. `"main" tid=1 Blocked
All these ANRs show that the main thread is either waiting or blocked. |
@samtstern hi, I have the same issue. ANR because of Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE in FirebaseInstanceIdReceiver "main" prio=5 tid=1 Native
Remarks:the resources that reference firebase are as follows: compileSdkVersion: 28, |
hi Everyone, ANR because of Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE in FirebaseInstanceIdReceiver "main" prio=5 tid=1 Waiting
//firebase remoteconfig
Please help me on it if anyone of you are having solution of this. |
Hi, we also got many report on play console with same error. |
Facing the same issue after upgrade FCM to 17.+ and targetSDKVertion to 28 |
Is there any fix for this? Got the same ANR in Android 9 only |
Any solutions? Lots of same ANRs in my google play console ANR list |
have same problem with firebase 18.2.0 |
any update? |
Maybe the QueueWork blocked by heavy work? |
@LiuDongCai @RijoshEnfin @smilewaver Have you tried upgrading your @samtstern Correct me if I'm wrong. |
BTW, beside the ANR log that everybody else has already shared, here is an extra log I got regarding this ANR:
|
i am using 20.1.5 version of firebase-messaging and still encountering the same issue. This anr is frequently reported on play console. |
Hi @zainForAndro , how about |
@samtstern & Support team, Thanks |
My earlier comments on this bug are, unfortunately, the best I will be able to offer. If anyone is able to find a minimal reproducible example for this there may be more to discuss: |
@samtstern "main" prio=5 tid=1 Native
|
@tuancoltech |
I'm glad you're not working for Boeing. |
We meet the same thing in the project and update it to 20.1.7 is useless. This problem seems to have existed for at least a year, do you have the plan to solve it? |
Same issue |
+1 |
Same issue,do you have the plan to solve it? |
Hi,bro. Did you see after the app was released that the GooglePlay console didn't have this problem? |
My app use a lot of high priority fcm notification with only payload.I wonder if this happens when user click the notification to open the app or when user receive the notification then the app is process is started? |
I've tried to change the fcm notification priority from high to normal, all the ANRS caused by FirebaseInstanceIdReceiver disapeared, except one which has a stacktrace that I think could be resolved. But the notification recieve rate dropped about 10%. |
I've also tried to change the fcm notification priority from high to normal, the ANRS caused by FirebaseInstanceIdReceiver decreased a lot. But the notification receive rate dropped about 30%, which has a huge affect to our app... |
Hi, @mwshubham, I check the release note and it says "Fixed an issue that caused an app to crash when a user tapped on a received notification." I'm aware that it solves the crash instead of ANR issues. I just want to confirm if the updates will help to reduce ANR. Also, I read the comments from @samtstern which says the devices with >26 will trigger more ANRs instead of <26'devices. But as I see in the play console, many ANRs are reported every day from Android 6 devices with SDK 23. And it's been a year since last suggestion. Do we have any updates on this issue? Looking forward to your reply :) |
We are still getting this error even after
It is still coming in the latest version "com.google.firebase:firebase-messaging:20.2.4" |
Same as @arsundram. We have already updated to 20.2.4 but still getting this kind of ANRs at the same high rate. |
ANR +1 |
I updated to
|
I was also getting the same ANR(as it mentioned in early comments). So i'm sharing my finding here with you all guys to reduce this ANR. Memory Leak can be one reason for emitting this com.google.firebase.iid.firebaseinstanceidreceiver ANR. Hope this help to all you guys. |
@pratyesh Interesting. |
This issue is closed and is not asigned to anyone. I think that the best is continue comments in this issue: Thanks 👍 |
@tuancoltech So same way if you guys start looking on your Memory Leak issue and after fixing this then surely your ANR will get reduce. Thanks. |
The text was updated successfully, but these errors were encountered: