`__fbBatchedBridge is undefined` when loading a project with HMR in iOS simulator
See original GitHub issueSteps to reproduce:
- Open Expo XDE
- Create new tab-based project
- Run on iOS Simulator (app now works)
- Enable hot reload (hot reload now works)
- Exit simulator
- Run on iOS Simulator again
Expected result: Application will run
Actual result:
App crashes with Unable to execute JS call: _fbBatchedBridge is undefined
The only way to fix Expo client on simulator is to delete it from home screen and install again. Also, if you disable Hot Reload before quitting simulator, this problem will not appear. So to sum up, it really seems that exiting iOS Simulator with Hot Reload enabled is the sole trigger of this problem.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Unable to execute JS call: __fbBatchedBridge is undefined
It is an iOS simulator rather than an emulator, and cannot run the ARM CPU instructions used to build a release build for...
Read more >fbBatchedBridge is undefined : r/reactnative - Reddit
Update: When I uncomment the "jsCodeLocation" line to load from disk, then try to build/run that from XCode onto my iPhone, I get...
Read more >https://floobits.com/tyrus.brenc/raymond_tyrus/raw...
isInitialized=false; module.exports=undefined; throw e;}} function unknownModuleError(id){ var ... try restarting the packager or running "npm install".
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
iOS Expo Client v1.18.2 is going out today (simulator and ExpoKit) and later this week (app store). It includes the aforementioned fix for this issue. Let me know if you’re still seeing any trouble here.
Tentative fix is here: https://github.com/expo/expo/commit/b383dc4add1f7112de8b67bbaaa3e96c523507cb
I’m double checking with the original author to make sure I’m not breaking something else. Assuming this is ok, I’ll ship this asap.