Firebase console show this while choose Crashlytics with iOS "We'll be listening for your app to communicate with our servers"

Question

Please guide me! Why Firebase console take much time to communicate with server. I'm waiting one and half hour to complete this takes. Anybody tell me what is the reason behind this issue or anyone facing this issue before.

Not show the Graph.

I am also having the same issue. I followed the documentation and used the latest sdk but still not working. I haven't found and answer too. I have just sent a message to Firebase Support on these matter, no response yet. — Rhusfer, Jul 30 '20 at 08:57
@Rhusfer I solved this problem by doing these steps : -> Uninstall App from simulator or Real Device -> Run the app on Simulator or Real device then stop running. -> And then Open the App that Install on Simulator or Real device. -> Open Firebase Console project And Refreshed it. — Honey Honey, Jul 30 '20 at 20:21
Just a reminder, ensure you've chosen the correct app in multi-apps project, see [here](https://stackoverflow.com/a/65545734/1074998) — 林果皞, Jan 03 '21 at 01:49

score 14 · Answer 1 · answered Aug 20 '20 at 12:28

14

Please make your app force fully crash 2-3 times, after disconnecting your app from Xcode.

This is what worked for me.

answered Aug 20 '20 at 12:28

Maheta Dhaval K

764
6
19

Honey Honey · Accepted Answer · 2021-12-12T11:18:34.647

8

In my case, I solved this problem by doing these steps:

Make sure you follows the all steps that mentioned in Firebase Documentation Crashlytics.
Use fatalError() for crash your app.
Uninstall App from simulator or Real Device
Run the app on Simulator or Real device then stop running.
And then Open the App that Install on Simulator or Real device.
Open Firebase Console project And Refresh it.

edited Dec 12 '21 at 11:18

answered Jul 30 '20 at 20:31

Honey Honey

233
2
12

I managed to get it work on simulator after deleting the app, then running with `fatal()` line prepared after few seconds later after launch, and the app was running without attaching to the Xcode. – Stanislau Baranouski Mar 16 '21 at 10:00

score 2 · Answer 3 · answered Jul 30 '20 at 16:15

2

This can happen as a result of several different issues, however they're usually connected to your app being unable to make the proper call to the Crashlytics settings endpoint. You can either write in to Firebase support, or feel free to start a private thread with me, and I can check your apps settings in the Firebase backend.

answered Jul 30 '20 at 16:15

Oleg Kodysh

986
6
13

Hi Oleg! I am having the same issue. Any chance you can take a look on my behalf as well? – Evorlor Aug 15 '20 at 21:34
I would need some of your apps info, such as bundle/Project ID, so you can either message me on a private thread, or post it here if you feel comfortable enough doing so. – Oleg Kodysh Aug 17 '20 at 13:54
I am also having same issue.How did you fixed it ? – poojathorat Apr 07 '21 at 09:53
@OlegKodysh,I am also having same issue.Can you check it ? – poojathorat Apr 07 '21 at 10:10
I followed each step but I am unable to see the crash report on Crashlytics Dashboard. Can you check it? – Rohit Singh Oct 28 '21 at 19:35
is there a generic way to resolve this @OlegKodysh – learner Mar 17 '23 at 17:29

score 1 · Answer 4 · answered Aug 17 '20 at 06:33

1

if you followed all steps as per latest crashlytics documents!

try forcing a crash directly with button click on initial view instead of just building and running your app

use fatalError() for crash your app

answered Aug 17 '20 at 06:33

shanth kumar

15
4

Firebase console show this while choose Crashlytics with iOS "We'll be listening for your app to communicate with our servers"

4 Answers4