You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks #16376
Reacted by Mauricio, Rhuan Santos, Alexander Harrison, Oren Klein, Davide Biagini, Carl Joachim Otvik, Stefano Falda, Arif Amirani, Djalma Araújo, Elliot Fleming and 299 more
Reacted by André Drougge, Aleksey Polukeev, Alejandro Perez, Stone Chen, Jon Garrison, mhq96, Rafael Araújo, Souad Maniani, rus0228, Jan Demel and 4 more
Reacted by XStable, Edmond Cheng, André Drougge, Aleksey Polukeev, Alejandro Perez, Stone Chen, J.Fischer, Nakul Saini, Iván González, Rafael Araújo and 8 more
I see this as well. Possibly related to #11196.
I believe this is what is also causing the app to crash when trying to reload; it fails with Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'This method must not be called before the JS thread is created'
I'm also getting this error from time to time on iOS 11 and I've got no idea how to debug this to give more information. Stacktrace doesn't help at all in this case.
Reacted by Guy Carmeli, Theodoros Kokosioulis, Ilia Sidorenko, YaroslavZhurba, Mark Ramotowski, Dan Tronin, Arsam Sarabi, Sébastien Mascha, José Sánchez, Yousef Ahmed and 30 more
Reacted by Jesus Miguel Flores, SkrewEverything, Vojtech Novak, Aron Gates, tsemerad, Akash R, Tommy, Jack Brown, Christian Mitchell, Guy Shahine and 100 more
Reacted by Simon Sturmer, Jakub, Juan Pablo Bedoya Martínez, rohovdmytro, Shubham Khuva, CodeMash, Andris Laduzans, Amir Diafi, Anthony, Alireza Goudarzi and 4 more
Reacted by Guy Carmeli, Ilia Sidorenko, YaroslavZhurba, Preet Patel, Simon Sturmer, rohovdmytro, Shubham Khuva, Firuzcan Hacıyev, Andris Laduzans, André Herculano and 2 more
Reacted by kabbi, Ilia Sidorenko, Zeeshan Ahmad, YaroslavZhurba, Preet Patel, Julio Orellana, Simon Sturmer, proudname, rohovdmytro, Shubham Khuva and 2 more
Reacted by Guy Carmeli, Ilia Sidorenko, Maksym Tymchyk, YaroslavZhurba, Greg Blake, Preet Patel, Lucien Perouze, Kailash Uniyal, Simon Sturmer, rohovdmytro and 6 more
Reacted by Simon Sturmer, Jafar Jabr, rohovdmytro, Shubham Khuva, Andris Laduzans, Anthony, Matthias Schmid, Evan Farrell and Bruno Melo
Reacted by YaroslavZhurba, Saravanabalagi Ramachandran, Preet Patel, Leon Truong, Sébastien Mascha, Yousef Ahmed, Simon Sturmer, rohovdmytro, Shubham Khuva, Andris Laduzans and 3 more
Reacted by Jesus Miguel Flores, LOG, SkrewEverything, Vojtech Novak, Aron Gates, Akash R, Tommy, Jack Brown, Christian Mitchell, Guy Shahine and 54 more
Please stop adding +1s, this is generating email notifications that don't add any information. Use the "add reaction" feature instead.
Reacted by Chetan Jadhav, Oren Klein, Mike Knapp, Djalma Araújo, Roman Sandu, Ruslan Urmeev, Neil, ivan titkov, Richard-Cao, Tung Nguyen and 502 more
Reacted by Ali Hamza, Pratham Mehta, Terry Xu, Ilya Lukyanov, Celento George, Tommy, Peace, Célio Garcia, isno, Dan Cork and 39 more
Reacted by fschai89, Sarath, Omar Salah Elboredy, Lewis Yuburi, Rory Pickering, Baltuonis, Emma Jamieson-Hoare, mursang, Gabriel Ferreira, Aron Gates and 78 more
Reacted by Pierre-Olivier Maugis, Aron Gates, Stephen, Waqar A, Dan Cork, Enrique Viard, solonifer, Shaun Cains, David Somers, Tom Daniel and 39 more
Reacted by Jean Paul Maradiaga, Dan Cork, Edmond Cheng, Shaz, kabbi, Ilia Sidorenko, Noel , Nikola, Julio Orellana, Try coke & pizza and 20 more
Reacted by Gleb Selyukov, Aron Gates, Stephen, Waqar A, Erfan Ebrahimnia, solonifer, Dan Cork, Shaun Cains, Tom Daniel, Shaz and 31 more
Reacted by Devkinggod, agung atidhira, Ilia Sidorenko, Jason Danielson, Nikola, Noel , Robin Binder, Greg Blake, Diogo Vianna, Elias and 27 more
Reacted by Juan, sarikabhimre18, WoongBi Kim, ansonc3, Ilia Sidorenko, Nikola, Noel , Temitope, Arnaud Ambroselli, Julio Orellana and 32 more
I just added react-native-device-info, and moved from rn 0.49 to 0.50. and now i found this bug. Don't know if it's the problem, but it's when i got this.
Reacted by Antoine Rousseau, matei-oltean, Martin Stankov, Jasper Kuperus, Mark Ramotowski, Dimitri Nicolas, kas, Oleksandr Naumkin, David Weinberg, Fernando Pascoal and 26 more
Reacted by Antoine Rousseau, Vijay Sapkota, matei-oltean, Martin Stankov, Jasper Kuperus, Mark Ramotowski, Dimitri Nicolas, kas, Oleksandr Naumkin, David Weinberg and 28 more
Same issue. The only package from the list above we use is react-native-sentry.
Reacted by Andy Wang, Lucas Mathioni, Salman, Micael Illos, Rohit Bhatia, Valentin Briand, Vitalii Tsurkan, Eduardo Spada, Florentin / 珞辰, Kacper Kapuściak and 4 more
Same issue here today i have started a brand new app and only package i have added
"native-base": "^2.3.3",
"react": "16.0.0",
"react-native": "0.50.3",
"react-native-fcm": "^10.0.3"
Reacted by Andy Wang, Lucas Mathioni, Micael Illos, Valentin Briand, Vitalii Tsurkan, Shaun, eneotujoe, Isaac and RODRIGO SARMENTO XAVIER
@dantman I started seeing the issue immediately after installing react-native-device-info, so I highly suspect the issue is related, at least in our case, to that specific package.
The only other package I am using react-native-keychain, which I installed quite a while ago without any issues, so it seems like a good bet.
Reacted by Noah Allen, Mingina, joelgetaction, Greg Blake, Manish Carpenter, Tejas Parab, Andris Laduzans, cltefnu and eneotujoe
@mwegener-com I have not created a config plug in because even though the warning comes I rarely get any crashes because of it. If you do create it I would appreciate the share
None of this works in 2022, on a fresh install of React Native 0.67.3
Reacted by John Szafraniec, Sʜɪᴍᴜʀᴀ Yū, Sergi Llonch, Mitchell Cooper, AbdulrhmenAE, William Bell, Felix Moser, Mitch Pash, Willy Rosa, Wesley Marra and 8 more
Using "react-native": "0.64.3" I am seeing this issue after installing a native module (Agora Livestreaming SDK) and running expo run:ios Mac Monterey & Xcode 13.3
I added two string values to Info.plist for the enable mic/camera permission text.
Besides that I have no other modules in project, and only imported expo libraries such as blurview for basic layout features.
I am seeing this issue now on loading the app through Metro now that I am in a bare workflow
Activity
almostintuitive commentedon Oct 15, 2017
Same here!
eggybot commentedon Oct 15, 2017
got this yellow issue for iOS
rizzomichaelg commentedon Oct 15, 2017
I see this as well. Possibly related to #11196.
I believe this is what is also causing the app to crash when trying to reload; it fails with
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'This method must not be called before the JS thread is created'jozan commentedon Oct 16, 2017
I'm also getting this error from time to time on iOS 11 and I've got no idea how to debug this to give more information. Stacktrace doesn't help at all in this case.
minikin commentedon Oct 16, 2017
+1
mkozhukharenko commentedon Oct 17, 2017
+1
antoinerousseau commentedon Oct 17, 2017
Please stop adding
+1s, this is generating email notifications that don't add any information. Use the "add reaction" feature instead.dantman commentedon Nov 7, 2017
Same issue. Here are the packages I use:
Given the intersection with @antoinerousseau's list, the possible locations for this bug are:
disjfa commentedon Nov 8, 2017
I just added react-native-device-info, and moved from rn 0.49 to 0.50. and now i found this bug. Don't know if it's the problem, but it's when i got this.
MilkBiscuit commentedon Nov 9, 2017
Same issue...
So it was not my fault ?
WhoJave commentedon Nov 10, 2017
Same issue... Do u have any solutions ?
SMJ93 commentedon Nov 14, 2017
Same issue. The only package from the list above we use is
react-native-sentry.bullantt commentedon Nov 15, 2017
Same issue here today i have started a brand new app and only package i have added
"native-base": "^2.3.3",
"react": "16.0.0",
"react-native": "0.50.3",
"react-native-fcm": "^10.0.3"
fishmwei commentedon Nov 16, 2017
@rizzomichaelg
+1
"react-native": "0.49.3",
app crashed when first load randomly.
anybody resolved it ??
thejacobseely commentedon Nov 16, 2017
@dantman I started seeing the issue immediately after installing react-native-device-info, so I highly suspect the issue is related, at least in our case, to that specific package.
The only other package I am using react-native-keychain, which I installed quite a while ago without any issues, so it seems like a good bet.
125 remaining items
mwegener-com commentedon Nov 3, 2021
@haibert It wouldn't be my first config plugin, but have you already finished it and might share your solution?
haibert commentedon Nov 3, 2021
@mwegener-com I have not created a config plug in because even though the warning comes I rarely get any crashes because of it. If you do create it I would appreciate the share
cloudorbush commentedon Nov 19, 2021
I'm getting the same error
fritzfr commentedon Nov 23, 2021
I have no idea what the meaning of the warning is, but this makes it go away:
https://amanhimself.dev/blog/rctbridge-required-dispatch-sync-to-load-warning/
liquidvisual commentedon Mar 15, 2022
None of this works in 2022, on a fresh install of React Native 0.67.3
billnbell commentedon Mar 20, 2022
0.67.3 this does not help. What does it mean?
W-Lawless commentedon Apr 21, 2022
Hello,
Using
"react-native": "0.64.3"I am seeing this issue after installing a native module (Agora Livestreaming SDK) and runningexpo run:iosMac Monterey & Xcode 13.3I added two string values to Info.plist for the enable mic/camera permission text.
Besides that I have no other modules in project, and only imported expo libraries such as blurview for basic layout features.
I am seeing this issue now on loading the app through Metro now that I am in a
bareworkflowl2aelba commentedon Jun 14, 2022
I'm from 2030 and this still does not fix. 😏
Nziranziza commentedon Jul 24, 2022
I am experiencing the same issue as well
YaoHuiJi commentedon Sep 28, 2022
... a new created 0.70.1 project has this issue too, it's funny, cause my 4 years old project doesn't have this issue.
I wonder is it safe to ignore this warning?
github-actions commentedon Mar 27, 2023
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.
github-actions commentedon Apr 3, 2023
This issue was closed because it has been stalled for 7 days with no activity.