Titanium JIRA Archive
Appcelerator Community (AC)

[AC-6262] Firebase Crashlytics not displaying the uncaught exceptions

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionNot Our Bug
Resolution Date2019-06-26T09:41:28.000+0000
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelscrash, exception, firebase
Reporterpravsrivastava
AssigneeShak Hossain
Created2019-05-21T14:49:17.000+0000
Updated2019-06-26T09:41:28.000+0000

Description

we are trying to use Firebase Crashlytics (github.com/hansemannn/titanium-crashlytics) as a crash reporter, but titanium catches all error in the event listener uncaughtException. Therefore, no crashes are sent to Firebase. I am expecting the exception to be displayed in firebase, but it is not appearing in firebase.

Attachments

FileDateSize
Screen Shot 2019-05-29 at 1.08.03 PM.png2019-05-29T17:22:39.000+0000611587

Comments

  1. Sharif AbuDarda 2019-05-22

    Hello, This ticket needs some additional info, Like the SDK, module versions and platform versions. Also, some screenshots of the behavior you see in the firebase portal. Also, a trace log of the crash is also helpful. Thanks.
  2. pravsrivastava 2019-05-29

    SDK: 8.0.0GA module versions: iOS 1.2.2 iOS: 12.2 Android: API 23, 24, and 27 StackTrace: [ERROR] Script Error { [ERROR] column = 31; [ERROR] line = 83; [ERROR] message = "This is an Objective-C exception using for testing."; [ERROR] nativeStack = "3 KitchenSink0x00000001076964ad CLSExceptionRaiseTestObjCException + 40\n4 KitchenSink0x0000000107680449 -[Crashlytics setUserIdentifier:] + 0\n5 KitchenSink0x00000001076dd959 -[TiCrashlyticsModule throwException:] + 55\n6 CoreFoundation 0x000000010e3704cc __invoking___ + 140\n7 CoreFoundation 0x000000010e36da45 -[NSInvocation invoke] + 325\n8 TitaniumKit0x000000010a84fc89 -[KrollMethod call:] + 1385\n9 TitaniumKit0x000000010a84edcb __KrollCallAsFunction_block_invoke + 30\n10 TitaniumKit0x000000010a84ebdc KrollCallAsFunction + 496\n11 JavaScriptCore 0x0000000107ff18d3 _ZN3JSC16JSCallbackObjectINS_20JSDestructibleObjectEE4callEPNS_9ExecStateE + 515\n12 JavaScriptCore 0x00000001084974fc _ZN3JSC5LLInt9setUpCallEPNS_9ExecStateENS_22CodeSpecializationKindENS_7JSValueEPNS_17LLIntCallLinkInfoE + 380\n13 JavaScriptCore 0x0000000107fbcb63 llint_entry + 61648\n14 JavaScriptCore 0x0000000107fad8d9 vmEntryToJavaScript + 200\n15 JavaScriptCore 0x0000000108393730 _ZN3JSC11Interpreter11executeCallEPNS_9ExecStateEPNS_8JSObjectENS_8CallTypeERKNS_8CallDataENS_7JSValueERKNS_7ArgListE + 464\n16 JavaScriptCore 0x00000001085d8634 _ZN3JSC12profiledCallEPNS_9ExecStateENS_15ProfilingReasonENS_7JSValueENS_8CallTypeERKNS_8CallDataES3_RKNS_7ArgListE + 196\n17 JavaScriptCore 0x0000000107ff86fe JSObjectCallAsFunction + 478\n18 TitaniumKit0x000000010a82b3e2 __TiBindingEventProcess_block_invoke + 53\n19 TitaniumKit0x000000010a82b30a TiBindingEventProcess + 723"; [ERROR] sourceURL = "file:///Users/johorn/Library/Developer/CoreSimulator/Devices/C0902A53-6A08-40D4-A8F1-D60541DFC499/data/Containers/Bundle/Application/D11C0B72-9239-4D53-99F3-1B0770B839DE/KitchenSink.app/alloy/controllers/controls/toolbar.js"; [ERROR] stack = " at [native code]\n at sayHello(/alloy/controllers/controls/toolbar.js:83:31)"; [ERROR] toJSON = ""; [ERROR] }
  3. Rakhi Mitro 2019-06-26

    Hello [~pravsrivastava],
 I thought I’d check in to see how things are progressing with your need? Can you please test this issue on 8.0.2.GA and let us know the results.
  4. Rene Pot 2019-06-26

    Hi [~pravsrivastava], Firebase is a 3rd party solution and not officially supported. You can use the built-in event listener for uncaughtexception to send it to Firebase I'm sure, but I would recommend creating a ticket at the github repository of the module, not here. Our own crash analytics module ACA catches these out-of-the-box. This comes with the Pro subscription.

JSON Source