The title speaks for itself I think. I can't understand why this happens, but Firebase Crashlytics only logs crashes while the device is plugged in. Please help, as I'm fed up.
EDIT: Crashlytics core also throws a TimeoutException
Asked
Active
Viewed 256 times
0
-
Could you provide more information? You said firebase only receive crash report if you deploy it via USB, i guess it is development build variant. And firebase doesn't receive crash report when the app is installed with apk? would it be possible that it is different build variant and some wrong if-else statements that did not initialise the fabric? – hjchin Jul 07 '18 at 14:59
-
[Enabling debug mode](https://firebase.google.com/docs/crashlytics/force-a-crash#enable_debug_mode) might give you some clues. – Bob Snyder Jul 07 '18 at 15:08
-
Yeah sorry. The question is a bit unclear, hjchin,I mean that crash logging continues to work only while the app is deployed via USB and the device is still plugged in. Once I unplug the USB cable, crash logging no longer happens – EdrichVerburg Jul 07 '18 at 15:20
-
I have also enabled debug mode. Same issue – EdrichVerburg Jul 07 '18 at 15:21
-
perhaps try with other devices and emulator? I think this is a troubleshooting issue, i would suggest eliminate the possibilities one by one and reduce the scope. found something similar to your issues here. https://stackoverflow.com/questions/46546724/crashlyticscore-failed-to-execute-task-java-util-concurrent-timeoutexception https://stackoverflow.com/questions/48039580/crashlytics-timed-out-during-initialization – hjchin Jul 07 '18 at 16:05
1 Answers
0
yes you require some real time operations to be done on your application or else update google plugins in your amulator
Apurva Geete
- 35
- 1
- 11
-
Okay fine. When I perform real time operations when the device is not plugged in, however, No crashes still get logged. That is the question. – EdrichVerburg Jul 07 '18 at 14:56
-