anr - with repro steps - com.google.android.c2dm.intent.RECEIVE

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository. If you have a general question, need help debugging, or fall into some other category use one of these other channels:

• For general technical questions, post a question on StackOverflow with the firebase tag.
• For general Firebase discussion, use the firebase-talk google group.
• For help troubleshooting your application that does not fall under one of the above categories, reach out to the personalized Firebase support channel.

[REQUIRED] Step 2: Describe your environment

• Android Studio version: Arctic fox_
• Firebase Component: _BOM (29.0.3) (Database, Firestore, Storage, Functions, etc)
• Component version: _____

[REQUIRED] Step 3: Describe the problem

ANR in x.y.z PID: ## Reason: Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x11000010 pkg=x.y.z cmp=x.y.z/com.google.firebase.iid.FirebaseInstanceIdReceiver (has extras) }

Steps to reproduce:

its getting reported in play console for app at #1

i tried to reproduce it in sample app

put Thread.sleep(15000) in Application-> onCreate()

now send message when I sent “data message” issue not reproduced but when I sent “notification message” issue reproduced

** sent message every time after killing app process

WHY IS IT SO?? … if its because of time taken in Application’s onCreate then why its not occurring for both the cases.

Relevant Code:

mentioned above

[waseefakhtar]

It’s been the same for us. It’s the # 1 ANR in our app right now. And I see there were plenty of issues opened for it but I see them closed by the bot without any solution by anyone:

https://github.com/firebase/firebase-android-sdk/issues/3308 https://github.com/firebase/firebase-android-sdk/issues/3059

Has updating to the latest BOM solved it for anyone? I currently use these versions:

"com.google.firebase:firebase-common:16.0.3"
"com.google.firebase:firebase-analytics:18.0.2"
"com.google.firebase:firebase-plugins:1.1.0"
"com.google.firebase:firebase-iid:20.0.2"
"com.google.firebase:firebase-messaging:20.2.4"
"com.google.firebase:firebase-config:19.1.1"
"com.google.firebase:firebase-crashlytics:17.2.1"
"com.google.firebase:firebase-crashlytics-gradle:2.3.0"

[argzdev]

Hi @aapunain, unfortunately, I cannot answer your question. As of the moment, our engineers have a lot on their plates and this would require an engineer to investigate the code to check the logic with that case. If you’d like us to dig deeper on this, you could provide us with a realistic situation or an app without blocking the UI thread where this issue is experienced.

As a good practice, it is usually best not to block the main thread when performing operations, since this can cause unexpected issues. With that said, I’ll be closing this issue for now, feel free to open a new ticket with the said details. Thanks!