Skip to content
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

Could not get BatchedBridge Error on Windows 10, Running on Android Emulator or Device #17034

Closed
db-007 opened this issue Nov 30, 2017 · 1 comment
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@db-007
Copy link

db-007 commented Nov 30, 2017

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Steps to Reproduce

(Write your steps here:)

  1. Following instruction on this page https://medium.com/@jamesmarino/getting-started-with-react-native-and-firebase-ab1f396db549 clone github repo https://github.com/JamesMarino/Firebase-ReactNative.git
  2. cd into Firebase-ReactNative and issue npm i
  3. once npm installation is complete, open Android emulator and issue react-native run-android
  4. this will start React Packager, builds app successfully, install and start APK on emulator but then I get the error "Could not get BatchedBridge, make sure your bundle is packaged correctly"

Expected Behavior

Application should not show this error and should start normally

Actual Behavior

I get the error "Could not get BatchedBridge, make sure your bundle is packaged correctly" when running react-native run-android on either device or emulator.

batchedbridge
batchedbridge-reactpackager
batchedbridge-commandline-react-native run-android output

Reproducible Demo

https://github.com/JamesMarino/Firebase-ReactNative

@stale
Copy link

stale bot commented Jan 29, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 29, 2018
@stale stale bot closed this as completed Feb 5, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

1 participant