-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
iOS and Android app bundle failure #21420
Comments
Sane issue here, clean install today: brew update This fixed it: Also #21310 |
That did the job. I have been stuck the whole day |
A good amount of people in #21310 seem to think adding both, "@babel/core" and "@babel/runtime" solve this problem, but just like @andraskende above, "@babel/core" was not needed to get this fixed. The Babel docs also recommend using "@babel/plugin-transform-runtime" alongside this, but in devDependencies section of package.json |
Just in case this helps for the people that are fixing this issue, this is the exact timeline/steps it took for me to rectify this issue:
I also launched, |
I have reported to react-native-community/releases#45, hopefully we can have a new release soon. |
Environment:
MacBook Pro
Xcode v9.4
CLI v9.4
both Android and iOS app
Sept. 29/2018
Error when installing RN app with native code(react-native init AwesomeProject) and attempting to load the app with iOS simulator or Android device. I also followed the steps to resolve the issue, but still the same problem. This is not an older project but a new one.
.babelrc
{ "presets": ["module:metro-react-native-babel-preset"] }
package.json
{ "name": "sandboxios", "version": "0.0.1", "private": true, "scripts": { "start": "node node_modules/react-native/local-cli/cli.js start", "test": "jest" }, "dependencies": { "react": "16.5.0", "react-native": "0.57.1" }, "devDependencies": { "babel-jest": "23.6.0", "jest": "23.6.0", "metro-react-native-babel-preset": "0.47.0", "react-test-renderer": "16.5.0" }, "jest": { "preset": "react-native" } }
The text was updated successfully, but these errors were encountered: