Closed krisidmisso closed 4 months ago
:warning: | Missing Reproducible Example |
---|---|
:information_source: | We could not detect a reproducible example in your issue report. Please provide either:
|
Hi , you can try this solution in your node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js
i was also having the same error for android and i applied this patch for it and it worked for me.
moduleID: number,
methodID: number,
params: any[],
onFail: ?Function,
onSucc: ?Function,
): any {
const isDebuggingEnabled = (typeof atob !== 'undefined');
this.processCallbacks(moduleID, methodID, params, onFail, onSucc);
if(!isDebuggingEnabled)
{
return global.nativeCallSyncHook(moduleID, methodID, params);
}
}
thank you @vksgautam1986 it worked only on ios. But this modification resulted in other issues with reanimated (and skia). I had to do a full clean of the project to be able to run it again https://github.com/software-mansion/react-native-reanimated/issues/4673
I am facing similar issues with debuggers.
When I clean install the debug build (connected with metro as well), and then press debug, it opens the chrome developer menu, and results the above error (but from react-native-mmkv in my case).
LOG Running "XxxXxx" with {"rootTag":31}
info Opening developer menu...
info Launching Dev Tools...
BUNDLE ./index.js
LOG JavaScript logs will appear in your browser console
Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4 from /Users/arnab/dev/arnab/XXXXXX.:
None of these files exist:
* debugger-ui/debuggerWorker.aca173c4(.native|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
* debugger-ui/debuggerWorker.aca173c4/index(.native|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
at ModuleResolver.resolveDependency (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:114:15)
at DependencyGraph.resolveDependency (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/node-haste/DependencyGraph.js:277:43)
at /Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/lib/transformHelpers.js:169:21
at Server._resolveRelativePath (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/Server.js:1045:12)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Server._explodedSourceMapForBundleOptions (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/Server.js:993:35)
at async Promise.all (index 1)
at async Server._symbolicate (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/Server.js:945:26)
at async Server._processRequest (/Users/arnab/dev/arnab/XXXXXX/node_modules/metro/src/Server.js:418:7)
react-native-debugger
but not to flipper
hermes debugger.Mac (M1)
Android
(didn't check iOS)12L
Redmi Y2
0.216.0
0.72.4
yarn react-native doctor
:Common
✓ Node.js - Required to execute JavaScript code
✓ yarn - Required to install NPM dependencies
✓ Watchman - Used for watching changes in the filesystem when in development mode
Android
✓ Adb - Required to verify if the android device is attached correctly
✓ JDK - Required to compile Java code
✓ Android Studio - Required for building and installing your app on Android
✓ Android SDK - Required for building and installing your app on Android
✓ ANDROID_HOME - Environment variable that points to your Android SDK installation
iOS
✓ Xcode - Required for building and installing your app on iOS
✓ Ruby - Required for installing iOS dependencies
✓ CocoaPods - Required for installing iOS dependencies
✓ ios-deploy - Required for installing your app on a physical device with the CLI
✓ .xcode.env - File to customize Xcode environment
Errors: 0
Warnings: 0
+1
We used react native debugger with HERMES turned on, had to add react-native-devsettings to make it working. The default HERMES debugger isn't as advanced. Can't use flipper due to long old battle of Firebase vs flipper issues. Also was reading this discussion regarding flipper and react native: https://github.com/react-native-community/discussions-and-proposals/blob/main/proposals/0641-decoupling-flipper-from-react-native-core.md.
Seems like since bumping to 0.72.7 and the packages, we have lost ability to even debug via the react-native-debugger :c
RN devsettings doesn't seem to work with v0.73+, so we cant use react-native-debugger anymore, how are we supposed to debug, access the redux state etc... ?
use this instead of flipper: react-native start --experimental-debugger
(press j
in the terminal after running the app)
I did, but the app crashes on startup with the saame error you posted in the initial post.
and in the console:
Unable to resolve module ./debugger-ui/debuggerWorker
also, I dont think the experimental debugger allows us to see the redux state
@Lakston it may be another 3rd party library that crashes your app. For me it was mmkv. I upgraded the framework to 0.73.x and removed that 3rd party library when debugging. For redux you can use redux-logger middleware. Not sure if Reactotron has been updated to use jsi buts its worth a shot if you like to mod your redux store
Description
"Calling synchronous methods on native modules is not supported in Chrome" on the latest version 0.72.4. Debugging made impossible with the new versions of RN:
React Native Version
0.72.4
Output of
npx react-native info
Steps to reproduce
Create a new version of RN with Firebase
Snack, screenshot, or link to a repository