After opening my React Native project in Expo, I get a "New update available, downloading..." infinite loading on the Android emulator.
I tried restarting the server and restarting the emulator, expecting to see the actual content of my React Native application.
I managed to solve this problem by following these steps:
Stop the server.
Uninstall Expo on Android emulator.
Run npm start.
Reopen the application on Android emulator.
I created an App in Expo first but for bluetooth printing i shift my project to react-native
then after some time i want to update something but react-native android build was failing so i just copy project removed print button and build in expo but the problem is now the already build apk hiding that print button sometimes why it is happening both are different apk different platform
one is react-native cli other is expo cli why it is syncing with each other.
Anybody having this problem ?
I want to run my React Native app in the iOS emulator. Here is what I done so far:
I installed XCode, along with its command line tools, and can bring up the emulator without issue.
I created an empty React Native app using the Expo CLI, per the instructions here. https://facebook.github.io/react-native/docs/getting-started. I am running on Node v10.0.0 on a Mac.
Afterwards I install all the necessary dependencies.
I then run "sudo npm run ios". This fires up the Metro Bundler as well as the iOS simulator. The Simulator loads up after about 5 minutes of waiting, but my app does not start up.
What am I missing here?
I should note that I prefer to stick with Expo, so I'd prefer not to have to eject.
Hey can anyone help me with react-native and mapbox?
Whenever I'm running the command react-native run-android it first starts the app and immediately the app gets crashed
After an attempt to use the adb tool to pull an updated sqlite database to my android emulator, I am unable to run my app on that emulator. Instead of showing the main screen of my app, I get the "Welcome to React Native!" demo app. My source code does NOT contain this; all my App.js contains is a definition for a StackNavigator.
Here are the things I have tried in order to fix this:
Via the AVD console in Android Studio, delete and recreate the image (Nexus 5, Android 6 with Google API)
Via the same console, use the Wipe Data option to try to reset it to a blank state.
Various npm commands, such as clean cache.
In addition, when I attempt to run react-native run-android from the command line, it usually immediately exits after building the application.
Can anyone give me any idea what I can do just to simply run my app on the emulator?
App source is at https://github.com/fergusonjason/soccerstats if that is any help.
(Yes, I realize this sounds stupid. Why it would replace an app I've been working on for 3 weeks with the react-native starter app is beyond me).
Jason
Assuming your java script bundler is up and running with react-native start you can try to reload by running adb shell input keyevent KEYCODE_MENU in another terminal and pressing reload after the Dev Menu shows up in the emulator.
Then be sure to check in your terminal where you ran the start command, if the Bundling log shows up. If it doesn't shows up, then perhaps you have another bundler running, which needs to be terminated before you can run your project
After trying several things, I ended up forcing a rebuild of index.android.bundle:
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/
It's possible that I had never staged or committed any updates of this file to the github repo.
Thank you to Aureo Beck for attempting to help me.