Debugger causes error in chrome and blank screen in App
See original GitHub issueEnvironment
OS: macOS 12.3.1
CPU: (10) x64 Apple M1 Max
Memory: 81.19 MB / 64.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
Yarn: 1.22.11 - ~/.nvm/versions/node/v14.17.0/bin/yarn
npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: ^17.0.2 => 17.0.2
react-native: 0.68.0 => 0.68.0
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
Description
When I start debug in Chrome, the App screen is blanked out and I get this error message in the react console:
None of these files exist:
* debugger-ui/debuggerWorker.aca173c4(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
* debugger-ui/debuggerWorker.aca173c4/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
at ModuleResolver.resolveDependency (/Users/kojo/Documents/Projekt/Egna/bas068/Bas/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:136:15)
and in chrome I get this:
index.bundle?platform=ios&dev=true&minify=false&modulesOnly=false&runModule=true&app=se.lejman.bask…:22543 Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
And a console log saying: Failed to mount LogBox within 1s
Reproducible Demo
Unfortunately I don’t have one that I can share…
Issue Analytics
- State:
- Created a year ago
- Comments:8
Top Results From Across the Web
Chrome debugger React.js app displays white screen and ...
I go back to Chrome and reload app (hit cmd + r to refresh). What I see: I get white screen and app...
Read more >New mobile chrome apps are just displaying a blank screen ...
New mobile chrome apps are just displaying a blank screen on ios sim and ios devices. 427 views ... The remote debug tool...
Read more >9 Proven Methods to Fix the WordPress White Screen of Death
The WordPress White Screen of Death is almost always caused by PHP code errors or memory limit exhaustion. Another possible cause is a...
Read more >How to Fix the WordPress White Screen of Death (9 Methods)
Enabling Debug Mode · Save the changes and upload the updated file. · Now return to the browser and refresh the screen. ·...
Read more >Chrome White Screen: Get it Back to Normal With 7 Solutions
Google Chrome's blank screen error can be due to a corrupted browser cache. Therefore, clearing Chrome's cache might fix things. 3. Rename the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
have upgraded the react native version 0.63.xx to 0.67.xx using command ‘npx react-native upgrade’ iOS working as expected with and without debugger but in android it is working as expected without debugger but if try to connect with debugger i.e react-native-debugger, chrome browser, firefox browser the android app getting crashed and throwing below error and warnings
After try to connect with debugger
File name: ExceptionsManager.js:149 Error: i. Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.
Consider providing alternative methods to expose this method in debug mode, e.g. by exposing constants ahead-of- time. ii. Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4 from /Users/userdirectory/Projects/MyApp/.:
None of these files exist:
LOG JavaScript logs will appear in your browser console
I’m also having this issue.