Crashlytics truncates React Native stack trace

[douglasjunior]

Its possible to prevent crashlytics to truncate the React Native stack trace? (I'm not using Hermes)

Example:

Fatal Exception: com.facebook.react.common.JavascriptException: TypeError: console.tron.log is not a function. (In 'console.tron.log(t)', 'console.tron.log' is undefined)

This error is located at:
    in M
    in o
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in RCTScrollView
    in C
    in ScrollView
    in Unknown
    in S
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in f
    in B
    in Unknown
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in PanGestureHandler
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in RCTView
    in Unknown
    in M
    in Unknown
    in RNSScreen
    in S
    in Unknown
    in _
    in w
    in Unknown
    in RNSScreenContainer
    in ScreenContainer
    in Unknown
    in RCTView
    in Unknown
    in Unknown
    in T
    in RCTView
    in Unknown
    in v
    in RCTView
    in Unknown
    in Unknown
    in P
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in We
    in Unknown
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in PanGestureHandler
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in RCTView
    in Unknown
    in M
    in Unknown
    in RNSScreen
    in S
    in Unknown
    in _
    in w
    in Unknown
    in RNSScreenContainer
    in ScreenContainer
    in Unknown
    in RCTView
    in Unknown
    in Unknown
    in T
    in RCTView
    in Unknown
    in v
    in RCTView
    in Unknown
    in Unknown
    in P
    in Unknown
    in Unknown
    in Xe
    in Unknown
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in PanGestureHandler
    in Unknown
    in RCTVie<truncated: 1782 chars>
       at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:83)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
       at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:883)
       at android.os.Handler.dispatchMessage(Handler.java:100)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loop(Looper.java:224)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
       at java.lang.Thread.run(Thread.java:919)

See the in RCTVie<truncated: 1782 chars line, this prevents me from figuring out the row and column where the error occurred.

When the stack trace is smaller, the rows and columns appear normally:

Fatal Exception: com.facebook.react.common.JavascriptException: Error: Text strings must be rendered within a <Text> component.

This error is located at:
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in w
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in S
    in Unknown
    in k
    in Unknown
    in Unknown
    in Unknown
    in Unknown
    in C
    in RCTView
    in Unknown
    in Unknown
    in f
    in y
    in RCTView
    in Unknown
    in RCTView
    in Unknown
    in E, stack:
Al@27:62065
$a@27:81226
Xa@27:81109
Ya@27:80976
Wa@27:80741
Ha@27:77740
Ha@-1
xt@27:26276
Re@27:93487
Ce@27:12979
Le@27:13356
receiveTouches@27:14149
value@51:3579
<unknown>@51:758
value@51:2582
value@51:730
value@-1

       at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:83)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
       at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loopOnce(Looper.java:226)
       at android.os.Looper.loop(Looper.java:313)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
       at java.lang.Thread.run(Thread.java:920)

Thanks!

[kristianstroka]

Did you solve this issue?

[douglasjunior]

Unfortunately, no.