App: [$250] Investigate πŸ’₯ Crash πŸ’₯ `.render`

Non-fatal Exception: io.invertase.firebase.crashlytics.JavaScriptError

Cannot read property β€˜validated’ of undefined

address at index.android.bundle:1:3232652 .render

Number of Crashes: 12

Device Information

  • Platforms: Android
  • App Versions: 1.1.86-5, 1.1.87-9, 1.2.11-2
  • Devices: samsung SM-G950F 9, samsung SM-G991U 12, realme RMX2001 11

Stacktraces

Android 1.2.11-2

.anonymous
._callTimer
.callTimers
.apply
.__callFunction
.anonymous
.__guard
.callFunctionReturnFlushedQueue
Android 1.1.87-9

.render
.finishClassComponent
.updateClassComponent
.beginWork
.performUnitOfWork
.workLoopSync
.renderRootSync
.performSyncWorkOnRoot
.flushSyncCallbacks
.scheduleUpdateOnFiber
.enqueueSetState
.anonymous
.setWithOnyxState
.sendDataToConnection
.anonymous
.tryCallOne
.anonymous
.apply
.anonymous
._callTimer
._callReactNativeMicrotasksPass
.callReactNativeMicrotasks
.__callReactNativeMicrotasks
.anonymous
.__guard
.flushedQueue
.invokeCallbackAndReturnFlushedQueue
Android 1.1.86-5
.render
.finishClassComponent
.updateClassComponent
.beginWork$1
.performUnitOfWork
.workLoopSync
.renderRootSync
.performSyncWorkOnRoot
.flushSyncCallbacks
.scheduleUpdateOnFiber
.enqueueSetState
.anonymous
.setWithOnyxState
.sendDataToConnection
.anonymous
.tryCallOne
.anonymous
.apply
.anonymous
._callTimer
._callReactNativeMicrotasksPass
.callReactNativeMicrotasks
.__callReactNativeMicrotasks
.anonymous
.__guard
.flushedQueue
.invokeCallbackAndReturnFlushedQueue

Internal Firebase Info

πŸ’₯ DO NOT EDIT THIS SECTION πŸ’₯

Crash IDs: de729788f9edff1f49f15d0662312d6c, 02604fb40d93d2fcccc055f74958b8b9, d45dd156888663d17674ae141f1ef344 Exception: Cannot read property 'validated' of undefined

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

I believe the logic is pretty simple at the moment; if a crash happens again, reopen it. We could add some more intelligence to only reopen if it’s happening on a version greater than those in the issue?