Hermes: YellowBoxInspector - TypeError: Cannot read property 'indexOf' of null

Created on 25 Jul 2019  路  6Comments  路  Source: facebook/hermes

Environment: Latest react-native generated by react-native init TestProject --template typescript, run in an Android emulator.

It can be triggered by calling console.warn() and then touching on the yellow warning box.

Emulator specs:

Name: Pixel_2_API_28

CPU/ABI: Google Play Intel Atom (x86)

Path: /Users/andre/.android/avd/Pixel_2_API_28.avd

Target: google_apis_playstore [Google Play] (API level 28)

Skin: pixel_2

SD Card: 512M

fastboot.chosenSnapshotFile: 

runtime.network.speed: full

hw.accelerometer: yes

hw.device.name: pixel_2

hw.lcd.width: 1080

hw.initialOrientation: Portrait

image.androidVersion.api: 28

tag.id: google_apis_playstore

hw.mainKeys: no

hw.camera.front: emulated

avd.ini.displayname: Pixel 2 API 28

hw.gpu.mode: auto

hw.ramSize: 1536

PlayStore.enabled: true

fastboot.forceColdBoot: no

hw.cpu.ncore: 4

hw.keyboard: yes

hw.sensors.proximity: yes

hw.dPad: no

hw.lcd.height: 1920

vm.heapSize: 256

skin.dynamic: yes

hw.device.manufacturer: Google

hw.gps: yes

hw.audioInput: yes

image.sysdir.1: system-images/android-28/google_apis_playstore/x86/

showDeviceFrame: yes

hw.camera.back: virtualscene

AvdId: Pixel_2_API_28

hw.lcd.density: 420

hw.arc: false

hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a7

fastboot.forceChosenSnapshotBoot: no

fastboot.forceFastBoot: yes

hw.trackBall: no

hw.battery: yes

hw.sdCard: yes

tag.display: Google Play

runtime.network.latency: none

disk.dataPartition.size: 6442450944

hw.sensors.orientation: yes

avd.ini.encoding: UTF-8

hw.gpu.enabled: yes
bug

Most helpful comment

Thanks for the bug report.

This is due to a different stack trace format emitted by Hermes, which causes the file name for native stack frames to be parsed as null. The React Native code which displays the YellowBox believes that the value must be a non-null string.

We'll work on finding a way to handle this correctly.

All 6 comments

Thanks for the bug report.

This is due to a different stack trace format emitted by Hermes, which causes the file name for native stack frames to be parsed as null. The React Native code which displays the YellowBox believes that the value must be a non-null string.

We'll work on finding a way to handle this correctly.

https://github.com/facebook/react-native/commit/6764385c8062fc647d016028351d8d7d28387ed5 checks for null before attempting to call indexOf and updates the corresponding Flow type definitions.

When that change propagates, it should prevent this crash from occurring.

there's any fix for that?

Experiencing that issue too.

 "react": "16.9.0",
 "react-native": "^0.60.5"

I'm getting this too: "react-native": "0.60.6"

Is facebook/react-native@6764385 release yet?

Having the same issue, only on Android API 29, below that error does not appear.

Is there a solution for this?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ghost picture ghost  路  5Comments

willholen picture willholen  路  4Comments

swabbass picture swabbass  路  3Comments

WilliamParks picture WilliamParks  路  3Comments

viky293 picture viky293  路  4Comments