-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS Warning: RCTBridge required dispatch_sync to load REAModule #3678
Comments
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
I see am seeing this as well now. |
+1 |
same |
This comment was marked as outdated.
This comment was marked as outdated.
Thank you, so the downgrade will help, but maybe someone will know what a patch or fixes for the current release |
I can also confirm that moving from |
Facing the same issue, will a downgrade work? I'm assuming it will but it wont fix the issue |
Hey, we are investigating this issue and working on a fix. Feel free to use 2.10.0 or call |
Hello, I stumbled upon the same issue today using 2.11.0 Just start a fresh project and follow react navigation documentation to add a drawer... The only missing piece on their docs is to add react-native-reanimated/plugin into babel... did a pod install and the only thing I got was that error, a regular stack works while a drawer will throw that error. The fix was to get back to 2.10.0 |
Same here using Reanimated 3-RC3 |
Downgrading to |
The offending PR is #3555. Fixed in #3698. If you encounter warning "RCTBridge required dispatch_sync to load REAModule", you have four options:
import { LogBox } from 'react-native';
LogBox.ignoreLogs(['RCTBridge required dispatch_sync to load REAModule']);
- + (BOOL)requiresMainQueueSetup
- {
- return YES;
- }
|
@tomekzaw Thank you for such a quick response, work and clarification! |
…3698) ## Description Fixes #3678. Reverts part of #3555 for Paper. On Paper, the warning "RCTBridge required dispatch_sync to load REAModule" was gone when I removed `requiresMainQueueSetup` method introduced in #3678. However, the PR description explicitly states that this method was added in order to eliminate the following warning: > This is because the `init` method was not present before and after adding it, it caused this warning: > > `Module RCTImagePickerManager requires main queue setup since it overrides init but doesn't implement 'requiresMainQueueSetup'. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.` However, after the removal of `requiresMainQueueSetup` no warning appears, so I assume that it is in fact not necessary to initialize REAModule on main queue, thus it's safe to remove `requiresMainQueueSetup`. On Fabric, removing `requiresMainQueueSetup` it crashes the app on reload, so I've left it as it is for now. We may address this inconsistency in a separate PR.
…3698) ## Description Fixes #3678. Reverts part of #3555 for Paper. On Paper, the warning "RCTBridge required dispatch_sync to load REAModule" was gone when I removed `requiresMainQueueSetup` method introduced in #3678. However, the PR description explicitly states that this method was added in order to eliminate the following warning: > This is because the `init` method was not present before and after adding it, it caused this warning: > > `Module RCTImagePickerManager requires main queue setup since it overrides init but doesn't implement 'requiresMainQueueSetup'. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.` However, after the removal of `requiresMainQueueSetup` no warning appears, so I assume that it is in fact not necessary to initialize REAModule on main queue, thus it's safe to remove `requiresMainQueueSetup`. On Fabric, removing `requiresMainQueueSetup` it crashes the app on reload, so I've left it as it is for now. We may address this inconsistency in a separate PR.
not to nitpick but the method is LogBox.ignoreLogs, not LogBox.ignore: import { LogBox } from 'react-native';
LogBox.ignoreLogs(['RCTBridge required dispatch_sync to load REAModule']); |
This issue has been fixed in #3698 and released in 2.12.0 so upgrade and you will never see this warning again. |
…oftware-mansion#3698) ## Description Fixes software-mansion#3678. Reverts part of software-mansion#3555 for Paper. On Paper, the warning "RCTBridge required dispatch_sync to load REAModule" was gone when I removed `requiresMainQueueSetup` method introduced in software-mansion#3678. However, the PR description explicitly states that this method was added in order to eliminate the following warning: > This is because the `init` method was not present before and after adding it, it caused this warning: > > `Module RCTImagePickerManager requires main queue setup since it overrides init but doesn't implement 'requiresMainQueueSetup'. In a future release React Native will default to initializing all native modules on a background thread unless explicitly opted-out of.` However, after the removal of `requiresMainQueueSetup` no warning appears, so I assume that it is in fact not necessary to initialize REAModule on main queue, thus it's safe to remove `requiresMainQueueSetup`. On Fabric, removing `requiresMainQueueSetup` it crashes the app on reload, so I've left it as it is for now. We may address this inconsistency in a separate PR.
I'm seeing this in a brand-new installation of RN (macOS Sonoma, iOS 17). Shouldn't this be fixed by now? |
@derwaldgeist Yes, this should be fixed. Which version of Reanimated exactly are you using? |
Oh, sorry. I just realized that this repo is related to a certain library. I just came here via Google and thought it was on the react-native repo itself. I just tried out RN, to check how far I can get on a Vision Pro (but the issue also occurred on iOS). |
@tomekzaw I got the same warning in the new version. "react-native": "0.73.3",
"react-native-reanimated": "^3.6.2", I think maybe it is related to the new version react-native.
|
@tuantvk I also have the same warning in version 0.73.3 A few days ago I built an app with version 0.73.2 and I didn't have any problems. 1 hour ago I built a new app with version 0.73.3 and started seeing this warning. Do you think this warning could cause problems later? Or we could just ignore it.
|
@correafederico25 Are you sure that it is the same message? I got |
Check facebook/react-native#42728 - it is fixed in 0.73.4, and not an issue with reanimated, but this is the first thing that comes up on google if you search 'RCTBridge required dispatch_sync' and leave out the RCTAccessibilityManager part |
Description
When the application starts, I get the following warning:
RCTBridge required dispatch_sync to load REAModule. This may lead to deadlocks
Steps to reproduce
Every time the application is launched
Snack or a link to a repository
Sorry
Reanimated version
2.11.0
React Native version
0.70.3
Platforms
iOS
JavaScript runtime
No response
Workflow
React Native (without Expo)
Architecture
No response
Build type
No response
Device
No response
Device model
No response
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: