So I have been struggling with a weird issue with my expo setup for about the last month or so. I created my project through Expo and when I use exp start in the terminal or try to load the project through Expo XDE, it hangs after dependency graph loaded. I thought it was an NPM issue (and worked on my coding environment for weeks trying to fix it) but then I created a new project using create-react-native-app and noticed there seems to be an issue with the connection with the simulator. When I instantiate a new project with create-react-native-app (not expo) I get this error exp://localhost:19000 — Error while loading: a server with specified hostname could not be found. (code - 1003) Here is a photo of what it looks like:
Then I tried to put the address of the project from the terminal into the simulator:
And it actually works! The app loads!
This is making me think there is a problem with the simulator's connection. Perhaps it is pointed to the wrong port? Using this method, I can run apps that were made from create-react-native-app but not my original projected I created through expo because that still gets hung and won’t launch the simulator. Projects created through Expo don't have an iOS file which is how you launch a create-react-native-app project (yarn run ios).
Any ideas about how I could go about fixing this?
Try uninstalling both Xcode & Expo.
Seems like the ports for the simulator are on different references of some kind.
Make sure that all of x-code, simulators, and expo local version are up to date before you launch the simulator after reinstalling Xcode & Expo.
Related
I have been building a react-native app using Expo. It has been running fine on the android emulator, but suddenly it will no longer load on the emulator. Here is the following error message:
Warning: Problem validating app.json: Unable to perform cache refresh for C:\User\AppData\Local\Expo\schema-45.0.0.json: Error: self signed certificate in certificate chain.
I am using Android Studio and developing on a Windows OS.
I have tried updating my expo-cli, using expo-doctor to fix my dependencies, deleting my package.lock file and reinstalling my modules, and clearing my expo cache. I have also tried clearing the data on my Android Studio device. None of these things have helped.
Also, my app runs fine in the expo web browser, so it is not a fatal error in my actual source code.
Any ideas about what is going on?
I believe this can be resolved by clearing the react-native packager cache.
Run: expo start --clear
You can add this to your package for future reference as well:
"start:clear": "expo start --clear",
Check the expo cli docs for additional info as well:
https://docs.expo.io/workflow/expo-cli/
I am new to coding. I recently had a coder update a React Native appI got it to run on Android with an emulator but there are multiple issues when getting the app to run on IOS. I am assuming the main issue is that I need to clean the react native app for IOS, and I have trouble finding information how to do this...WHat I tried was going to the iOS in the terminal and typing "xcodebuild clean" but errors still pursue....I tried opening up xxx. xcodeproj and I got an error that said "yogakit/yogakit.modulemap' not found". Then I tried opening up xxx.xcworkspace and it got an error saying that I need to update to Swift 5 but the update fails. I ve tried to research this issue everywhere but could not find a solution. What is it that I am doing wrong here? How do you take an updated code from Native React and get it to successfully run in Xcode?
I'm building a React Native application, and the javascript code updates are not reflecting in the ios Simulator. I have restarted the development server with react-native start and react-native start --reset-cache. I have used react-native-clean-project to clean the pods folder, node_modules, and various other caches. I tried reinstalling watchman. All these efforts have not worked.
The issue started about a week ago, until that time the javascript code was updating normally. And it currently will update when a file is changed with the hot reloads, but then when I rerun react-native run-ios it goes back to version of the javascript that was there previously.
Building the app directly from XCode doesn't work either. It still builds with the outdated javascript. Does anyone have any ideas on what may be causing this issue?
I have a Unity 5.6 2D project that I've created on my Mac (macOS Sierra). The game plays fine when I run it inside of Unity. However, when I "build and run", it appears to build fine (it creates the application), but it never runs. I have sent the project to another user who is able to successfully build his projects, but he has the same issue when trying to build mine. I've tried both an x86x64 and Universal build, but I have the same results. Application doesn't show in Activity Monitor either.
HELP - I need to turn this in for a class!!!!
Thanks!
Thank you #Programmer and #Coolq B for all your help. I was able to get it to work by exporting everything out of my project, and import it into a new project. Clearly, there was something corrupt in the original project.
I'm trying to generate release version of my app using React-native :
./gradlew assembleRelease
It's progress until app::bundleReleaseJsAndAssets gets stuck at 93% and never progress. I dont have any error on terminal.
About OS I'm on Mac OS.
issue reported https://github.com/facebook/react-native/issues/10078
If you are using realm, please consider that comment:
:app:bundleReleaseJsAndAssets was trying to bundle the default.realm* in the root folder generated from the tests in jest... So it was hanging there.
It couldn't decompile them or whatever. So i just deleted them and it worked again
I used to have realm in my project but removed it. I still had files not tracked by git, hanging around. I simply removed everything related to realm and it worked again
If you are building the react native app in android studio and you are stuck at
app::bundleReleaseJsAndAssets never progress
It could be the issue with "CMD" in the android studio. Please Make sure you install the plugin.
I'm able to resolve the issue.