react-native: RN 0.72-rc.3 release builds crash on startup due to bytecode version mismatch

@cortinico i can confirm the hermesc on linux is bytecode version 95. i don’t know how react-native nowadays publishing/generating hermesc, i can help to investigate further tomorrow.

$ yarn why react-native
yarn why v1.22.19
[1/4] Why do we have the module "react-native"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "react-native@0.72.0-rc.3"
info Has been hoisted to "react-native"
info This module exists because it's specified in "dependencies".
info Disk size without dependencies: "68.81MB"
info Disk size with unique dependencies: "123.58MB"
info Disk size with transitive dependencies: "192.34MB"
info Number of shared dependencies: 195
Done in 0.83s.

$ ./node_modules/react-native/sdks/hermesc/linux64-bin/hermesc -version
LLVM (http://llvm.org/):
  LLVH version 8.0.0svn
  Optimized build

Hermes JavaScript compiler.
  Hermes release version: 0.12.0
  HBC bytecode version: 95

  Features:
    Debugger
    Contiguous Heap
    Zip file input

for reference the hermesc -version on macos is as following, we can seen both hermes release version and hermes bytecode version are different:

$ ./node_modules/react-native/sdks/hermesc/osx-bin/hermesc -version
LLVM (http://llvm.org/):
  LLVH version 8.0.0svn
  Optimized build

Hermes JavaScript compiler.
  Hermes release version: for RN 0.72.0-rc.3
  HBC bytecode version: 94

  Features:
    Zip file input

@cortinico

1. npm list -g and yarn global list both show a few packages and none of them are related to React Native in any way
2. No, and no.

Do you guys have an ETA for when you’re making a release that includes this fix?

This will be included in the next RC sometime next week or the following one

Thanks for the clarification @Kudo. I believe this is an instance of cache poisoning on CircleCI where we reused hermesc from the latest build from main, when we should be isolating caches for each RN version. Fix is incoming

By the way, I followed the steps I wrote above to reproduce the error when getting the logcat above for you, so yeah the repro steps are exact, at least on my machine.

@cortinico

05-15 15:07:39.031 12479 12505 E AndroidRuntime: FATAL EXCEPTION: mqt_js
05-15 15:07:39.031 12479 12505 E AndroidRuntime: Process: com.testapp, PID: 12479
05-15 15:07:39.031 12479 12505 E AndroidRuntime: com.facebook.jni.CppException: Compiling JS failed: Wrong bytecode version. Expected 94 but got 95 Buffer size 761500 starts with: c61fbc03c103191f5f0000009f3ef2b1
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at com.facebook.jni.NativeRunnable.run(Native Method)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:236)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
05-15 15:07:39.031 12479 12505 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:923)