Getting Hermes error when calling Realm.objects even if Hermes is disabled

[jerome-archzoo]

How frequently does the bug occur?

Sometimes

Description

This happens sometimes in production release when unlocking the device after a period of idle (typically a few hours), we found that the error message came from Hermes engine inside "createJSExecutor" function, however we are pretty sure Hermes had been disabled. This error did not happen before we upgraded realm-js from 10.9.1 to 11.10.2, but I'm not sure if it really related to the upgrade.

React Native version: 0.73.4

Stacktrace & log output

Device
Model:iPad (5th generation)
Orientation:Face Up
RAM free: 65.84 MB
Disk free: 1.31 GB



# Crashlytics - Stack trace
# Platform: apple
# Date: Wed Dec 04 2024 11:09:32 GMT+0800 (Hong Kong Standard Time)



Fatal Exception: RCTFatalException: Unhandled JS Exception: Error: getPropertyAsObject: property 'prototype' is null, expected an Object
0  CoreFoundation                 0x83f20 __exceptionPreprocess
1  libobjc.A.dylib                0x172b8 objc_exception_throw
2  <AppName>                      0x19dc58 RCTFormatError + 167 (RCTAssert.m:167)
3  <AppName>                      0x20e6b8 -[RCTExceptionsManager reportFatal:stack:exceptionId:extraDataAsJSON:] + 82 (RCTExceptionsManager.mm:82)
4  <AppName>                      0x20eee0 -[RCTExceptionsManager reportException:] + 154 (RCTExceptionsManager.mm:154)
5  CoreFoundation                 0x20814 __invoking___
6  CoreFoundation                 0x1f860 -[NSInvocation invoke]
7  CoreFoundation                 0x961dc -[NSInvocation invokeWithTarget:]
8  <AppName>                      0x1ceaa8 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 587 (RCTModuleMethod.mm:587)
9  <AppName>                      0x1d0bd4 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 196 (RCTNativeModule.mm:196)
10 <AppName>                      0x1d0820 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 298 (optional:298)
11 libdispatch.dylib              0x213c _dispatch_call_block_and_release
12 libdispatch.dylib              0x3dd4 _dispatch_client_callout
13 libdispatch.dylib              0xb400 _dispatch_lane_serial_drain
14 libdispatch.dylib              0xbf30 _dispatch_lane_invoke
15 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh
16 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread
17 libsystem_pthread.dylib        0x4934 _pthread_wqthread
18 libsystem_pthread.dylib        0x10cc start_wqthread



# Bugsnag
STACKTRACE



Error getPropertyAsObject: property 'prototype' is null, expected an Object 
    [native code] 
    ...
    /Users/runner/work/1/s/node_modules/react-native/Libraries/Core/Timers/JSTimers.js:230:17 
    /Users/runner/work/1/s/node_modules/react-native/Libraries/Core/Timers/JSTimers.js:111:6 _callTimer
    /Users/runner/work/1/s/node_modules/react-native/Libraries/Core/Timers/JSTimers.js:359:17 callTimers
    /Users/runner/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:433:34 value
    /Users/runner/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:113:26 
    /Users/runner/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:368:8 value
    /Users/runner/work/1/s/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:112:9 value
    [native code] value

Can you reproduce the bug?

Sometimes

Reproduction Steps

No response

Version

11.10.2

What services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

iPadOS 16.7.10

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

[kraenhansen]

Thanks for reporting the issue, as it might be relevant to someone in a similar situation.

It does however refer to a version published more than a year ago, in a codebase which is no longer in main, since v12 was a complete rewrite of the SDK (with minimal breakage to the API). As such, I'll close the issue as it won't realistically be fixed. Please upgrade to the latest major version and report back if you see similar behavior.

[jerome-archzoo]

@kraenhansen Can I have the reference to what you just mentioned with similar situation?

[kraenhansen]

Can I have the reference to what you just mentioned with similar situation?

I don't understand this request, please try rewording it. A reference - as a link?
What "similar situation" are you referring to?

[jerome-archzoo]

Can I have the reference to what you just mentioned with similar situation?

I don't understand this request, please try rewording it. A reference - as a link? What "similar situation" are you referring to?

@kraenhansen It would be helpful if you can provide any link to below

it might be relevant to someone in a similar situation