Chrome Debugging not woring with realm

[vinaykumar0339]

How frequently does the bug occur?

Always

Description

I have upgraded my React native version from 0.67.4 to 0.71.14. but here I am facing an issue with the async await code where some places working and some places are not in staging builds, But it working fine in debug modes.
but no response.

so I thought to disable Hermes in my project.
but realm having an issue with if I enabled Chrome debugging realm throwing errors like below screenshot
UNITO-UNDERSCORE!screenshot!UNITO-UNDERSCORE!88F32B1B-5B49-4FE0-BED2-D9093619E73F!

can anyone help on this quickly?

"realm": "12.2.1",
"react-native": "0.71.14",

node version: 16.18.0

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

while upgrading to 0.71.14 from 0.67.4. build failing with realm so upgraded from 10.9.1 to 12.2.1.
disable hermes enable chrome debugging.

Version

12.2.1

What services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

all versions

Build environment

Which debugger for React Native: ..
Chrome Debugger

Cocoapods version

1.12.0

[takameyer]

@vinaykumar0339 The Chrome Debugger is not compatible with Realm. You can only use the Hermes debugger, or you can use Safari to debug without Hermes.

[vinaykumar0339]

@takameyer thank you for your quick reply.

Do you have any idea about this Hermes staging builds issues facebook/react-native#41737
It would be more helpful to us if you have any idea on this 😊

[vinaykumar0339]

@takameyer I did not enable the Chrome debugger. Opened Safari to debug without Hermes.
for the source map of the code I modified the Appdelegate.mm file below

• (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
  {
  #if DEBUG
  NSURL *nsUrl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index.ios"];
  return [NSURL URLWithString:[[nsUrl absoluteString] stringByAppendingString:@"&inlineSourceMap=true"]];
  #else
  return [CodePush bundleURL];
  #endif
  }

but still same error coming.
Error: could not find the realm binary. as above image.

[kneth]

@vinaykumar0339 Can you provide a repro case for us?

[vinaykumar0339]

@kneth thanks for your reply it shows an error when we select Automatically Show Web inspector for JSContext
if you open the debugger after app loads its working fine only.

[kneth]

@vinaykumar0339 Do you observe the same behavior with our template app?