I just followed the instructions on docs/getting-started.html (with a real device).
Got a RedBox with:
Android error “Could not get BatchedBridge, make sure your bundle is packaged properly” on start of app
react-native run-android
There is a failed try to perform an adb command, revealed on the console with (French ouput):
'adb' n'est pas reconnu en tant que commande interne ou externe, un programme executable ou un fichier de commandes.
This prevents the script to run the regular adb reverse tcp:8081 tcp:8081 and a fallback is engaged without this necessary setting.
The fix is to help local-cli\runAndroid\adb.js to find adb.exe, the same way as local-clirunAndroidrunAndroid.js:
Replace:
const devicesResult = child_process.execSync('adb devices');
By:
const devicesResult = child_process.execSync( (process.env.ANDROID_HOME ? process.env.ANDROID_HOME + '/platform-tools/' : '') + 'adb devices');
This should fix issue #9336 as well, unless there are another causes.
thanks psam44
complete Path is:
[yourProjectFolder]node_modulesreact-nativelocal-clirunAndroid
Solution:
under "react-native" directory:
after run command "./gradlew :Examples:UIExplorer:android:app:installDebug" successfully,
run commnad "./packager/packager.sh" successfuly.
then click "UIExplorer App“ in the emulator or the device
I faced the same problem, it is because adb in not in your path.
Add adb in your path and it will work fine.
adb will be in
Hello, I am trying to run my react native app but i am not able to resolve the issue "Android error “Could not get BatchedBridge, make sure your bundle is packaged properly” on start of app" , is there any fix for it , i cannot find any solution on web either.
Hi , I also get the below error Execution failed for task ':app:processDebugResources'.
java.io.IOException: Could not delete path
Does anyone has a solution on how can i run the app on emulator ???
Also having this issue with the emulator. I have other issues with physical devices that make emulation my only choice.
Edit: This ended up being a JDK problem. After spending a few hours dealing with Java Error 1603 trying to reinstall it, this is resolved. I believe the cause of 1603 is that the Sun Java Updater was not removed from MSconfig startup entries, for anyone else who this bit of info might help.
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
@hramos
This bug is still current with:
React Native version: [email protected]
And the one-line fix is still the one given in the description.
(these automatic closings, without reading, are discouraging for me to contribute)
Most helpful comment
@hramos
This bug is still current with:
React Native version: [email protected]
And the one-line fix is still the one given in the description.
(these automatic closings, without reading, are discouraging for me to contribute)