RCTBridge required dispatch_sync to load RCTAccessibilityManager. This may lead to deadlocks

[correafederico25]

Description

When building a new project with React Native 0.73.3 I am getting the warning RCTBridge required dispatch_sync to load RCTAccessibilityManager. This may lead to deadlocks as soon as my app starts.

I tried creating a new app with version 0.73.2 and this warning disappears

This my package JSON file:

{
  "name": "AwesomeProject3",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "lint": "eslint .",
    "start": "react-native start",
    "test": "jest"
  },
  "dependencies": {
    "react": "18.2.0",
    "react-native": "0.73.3"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@babel/runtime": "^7.20.0",
    "@react-native/babel-preset": "0.73.20",
    "@react-native/eslint-config": "0.73.2",
    "@react-native/metro-config": "0.73.4",
    "@react-native/typescript-config": "0.73.1",
    "@types/react": "^18.2.6",
    "@types/react-test-renderer": "^18.0.0",
    "babel-jest": "^29.6.3",
    "eslint": "^8.19.0",
    "jest": "^29.6.3",
    "prettier": "2.8.8",
    "react-test-renderer": "18.2.0",
    "typescript": "5.0.4"
  },
  "engines": {
    "node": ">=18"
  }
}

Steps to reproduce

npx react-native@latest init AwesomeProject

React Native Version

0.73.3

Affected Platforms

Runtime - iOS

Output of npx react-native info

No

Stacktrace or Logs

WARN RCTBridge required dispatch_sync to load RCTAccessibilityManager. This may lead to deadlocks

Reproducer

No

Screenshots and Videos

[github-actions]

⚠️	Missing Reproducible Example
ℹ️	We could not detect a reproducible example in your issue report. Please provide either: If your bug is UI related: a Snack If your bug is build/update related: use our Reproducer Template. A reproducer needs to be in a GitHub repository under your username.

[fabOnReact]

react-native/packages/react-native/React/CxxBridge/RCTCxxBridge.mm

Lines 986 to 990 in 8a8f74b

	// Modules that need to be set up on the main thread cannot be initialized
	// lazily when required without doing a dispatch_sync to the main thread,
	// which can result in deadlock. To avoid this, we initialize all of these
	// modules on the main thread in parallel with loading the JS code, so
	// they will already be available before they are ever required.

[efstathiosntonas]

Getting the same after upgrading to 0.73.3, @fabOnReact care to explain why you linked the comments above?

[Jonnboy91]

Also getting the same after upgrading to 0.73.3 and I don't have the issue with 0.73.2 either.

[efstathiosntonas]

after applying a patch from PR and PR the issue is gone

[cortinico]

@cipolleschi can you look into this (potentially related to f39f34e)

[cipolleschi]

Fixed already:

• Pick requested in 0.73.4 => [RN][iOS] Fix warning when loading RCTUIManager and A11yManager #42734
• PR for main => Fix warning when loading RCTUIManager in the old architecture #42733