react-native: Calling synchronous methods on native modules is not supported in Chrome

Call the synchronized api, this appears:

React Native version:

React Native Environment Info: System: OS: macOS 10.14.6 CPU: (4) x64 Intel® Core™ i7-4578U CPU @ 3.00GHz Memory: 19.07 MB / 16.00 GB Shell: 5.3 - /bin/zsh Binaries: Node: 12.7.0 - /usr/local/bin/node Yarn: 1.3.2 - /usr/local/bin/yarn npm: 6.10.0 - /usr/local/bin/npm SDKs: iOS SDK: Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0 Android SDK: API Levels: 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 7, 8, 9 Build Tools: 22.0.1, 23.0.1, 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2 System Images: android-28 | Google APIs Intel x86 Atom IDEs: Android Studio: 3.5 AI-191.8026.42.35.5791312 Xcode: 11.0/11A420a - /usr/bin/xcodebuild npmPackages: react: 16.8.3 => 16.8.3 react-native: 0.59.10 => 0.59.10 npmGlobalPackages: react-native-cli: 2.0.1 react-native-create-library: 3.1.2

Steps To Reproduce

Describe what you expected to happen:

Snack, code example, screenshot, or link to a repository:

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 16
Comments: 39 (5 by maintainers)

Links to this issue

Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome - Stack Overflow

Commits related to this issue

Fix Appearance module when using Chrome Debugger Summary: The appearance module uses sync native module methods which doesn't work with the chrome debugger. This broke in 0.62: https://github.com/fac... — committed to facebook/react-native by TheSavior 4 years ago
Fix Appearance module when using Chrome Debugger Summary: The appearance module uses sync native module methods which doesn't work with the chrome debugger. This broke in 0.62: https://github.com/fac... — committed to facebook/react-native by TheSavior 4 years ago

Most upvoted comments

experiencing exact same issue. It only happened after transition to react-native 0.65.1 worked totally fine before that. Tried to apply different solutions, but they all lead to some other issues.

1+ facing the same issue after just upgrading to 0.65.1

+14

meshackjr on Sep 16, 2021

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

+13

stale[bot] on Oct 4, 2020

Same here. Removing calls to Appearance in version 0.62 solved it. I reverted back to using expo/react-native-appearance package

+11

nechmads on Apr 1, 2020

same issue on 0.65.1

+10

3KINGZ on Sep 19, 2021

Ran into this problem when upgrading to react native 0.62.0. Still present.

We are using react-native-device-info version 5.5.3. However it seems the issue was caused by the new Appearance.getColorScheme() code. I removed my calls to it and its working fine now.

KarlHerler on Mar 30, 2020

hey folks, thanks for surfacing this issue - we are putting it in front of the team that worked on it so that they can help us understand how to get this fixed.

kelset on Apr 6, 2020

experiencing exact same issue. It only happened after transition to react-native 0.65.1 worked totally fine before that. Tried to apply different solutions, but they all lead to some other issues.

alex-noel on Sep 16, 2021

Same issue on 0.65.1 please help us

EHRdev on Sep 21, 2021

I’m getting this warning in the default ReactNative demo on running the application in debug mode (No dependencies added).

},
 "dependencies": {
   "react": "17.0.2",
   "react-native": "0.65.1"
 },
 "devDependencies": {
   "@babel/core": "7.15.5",
   "@babel/runtime": "7.15.4",
   "@react-native-community/eslint-config": "2.0.0",
   "babel-jest": "26.6.3",
   "eslint": "7.14.0",
   "jest": "26.6.3",
   "metro-react-native-babel-preset": "0.66.0",
   "react-native-codegen": "^0.0.7",
   "react-test-renderer": "17.0.2"
 },

What’s the fix? I don’t want to edit the MessageQueue.js to suppress this.

Downgrading to 0.64 doesn’t cause this issue.

deepakaggarwal7 on Sep 11, 2021

@deepakaggarwal7 just created a new issue related to this with detailed info, feel free to comment there if you need

betoharres on Sep 13, 2021

@nomi9995 @stdavis I opened a new Issue, since I think the new one is related to the AuthRequest and not this one. https://github.com/expo/expo/issues/12712

madroneropaulo on Apr 23, 2021

@i7soft Did you ever find a solution for this problem? Currently experiencing this right now, and not being able to use a debugger is rough.

update: Our problem ended up being related to a rollbar version upgrade, https://github.com/rollbar/rollbar-react-native/issues/101

TheNoodleMoose on Nov 12, 2019

why is this closed when it still occurs ?

29er on Jun 16, 2021

Can confirm that this happens with the Appearance API on the latest version (0.62)

Johan-dutoit on Apr 6, 2020