Skip to content

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

Description

@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

Captura de pantalla 2024-01-30 a la(s) 05 10 08

Activity

  1. github-actions commented on Jan 30, 2024

    @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.
  2. fabOnReact commented on Jan 30, 2024

    @fabOnReact
    Contributor
  3. efstathiosntonas commented on Jan 30, 2024

    @efstathiosntonas

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

  4. Jonnboy91 commented on Jan 31, 2024

    @Jonnboy91

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

  5. efstathiosntonas commented on Jan 31, 2024

    @efstathiosntonas

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

  6. cortinico commented on Jan 31, 2024

    @cortinico
    Contributor

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

  7. cipolleschi commented on Jan 31, 2024

    @cipolleschi
    Contributor
  8. joeljerushan commented on Feb 1, 2024

    @joeljerushan

    "react-native": "0.73.3" still same

  9. kulakowka commented on Feb 2, 2024

    @kulakowka

    I have the same issue.

    "react-native": "^0.73.2",
  10. andriiradkevych commented on Feb 2, 2024

    @andriiradkevych

    When 0.73.4 version with fix will be released ?

  11. jomavazquez commented on Feb 2, 2024

    @jomavazquez

    Me too:

    Creating a project now using:
    npx react-native init MyProject --template react-native-template-typescript

    this downloads 0.73.3 RN version, and then without any modification, I get the error in IOS.

    Waiting this new PR approved in 0.73.4 or whatrver. Thank you

  12. Titozzz commented on Feb 2, 2024

    @Titozzz
    Collaborator

    Version 0.73.4 with the fix with be released Monday!
    In the meantime you should be safe ignoring that warning.

    Sorry for the inconvenience

  13. andriiradkevych commented on Feb 5, 2024

    @andriiradkevych

    @Titozzz you can't ignore it , for example my app just doesn't work because of this issue . Is it planned to release it today ?

  14. olivierlesnicki commented on Feb 11, 2024

    @olivierlesnicki

    +1

  15. ChromeQ commented on Feb 11, 2024

    @ChromeQ

    @olivierlesnicki This issue is fixed in version 0.73.4 - this issue should be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions