React Native Expo Building Javascript Bundle stuck at 99 - javascript

I'm running my react-native app using expo on my mobile.
However, when I start the packager and connect to expo app on my mobile, it's stuck at 99% for building javascript bundle process.
There has been no code change to cause this.
I have tried re-installing my node modules and restarting my packager after cleaning cache.
What is causing this issue?

Would you mind sharing a screenshot? Did you try pressing i to start the iOS simulator (if you're using iOS) Personally, I use the Expo XDE to start my expo projects. As a last resort, you can always clone your project and start from there

I had a similar problem. Turned out that i had to press enter in my console screen so it continued exporting to the expo app

It works for me.
adb kill-server
adb start-server

Related

Error running expo android app in production mode - React-native

Pretty new to expo so not sure what this error means am getting this when I run expo in production mode
After I try reloading the app it gets stuck at the new update downloading
Would be highly appreciated if anyone can help! Let me know if any more details needed.
Are you running the app in expo go (mobile) or Android emulator ?
If expo go, then connect to tunnel from metro bundle and then scan it again

Failed to launch emulator. Reason: No emulators found as an output of `emulator -list-avds`. , Failed to install the app

enter image description here
Im new to React-Native and this is driving me insane, I just want to launch the project in the and view the project in the emulator so I can just start coding, I have tried downloading the latest version of JDK, which is apparently not even needed since android studio comes bundled with its own version & also how do I know what version of JDK my android studio comes bundled with ?
I have been trying to fix this for days now, I even got Blue screen of death when after I messed around with the enviroment variables so now I am desperate and want someone to point me in the right direction.
React native install app on a single running device. Make sure your emulator is in running condition
check all connected devices which are eligible for installing using a command
adb devices
one device at a time
Please check your JDK path for android and ios, if all things are correct the see the project files in the project.
Then run your project.
I hope it runs.

why my app automatic disconnect with expo CLI?

i am using react native expo but I am facing issue in starting the app , when the app start and the expo stopped working after it builds complete and I have to again restart the complete package and then it work again only for 1 minutes or less time , also I have upgraded my node JS chrome 8. to 10 I think the issue is from Node.js side
Try deleting and re-installing expo. Something similar was happening to me and it fixed the issue.

What happens with my app if one day Expo is unavailable

I am building an app in react native detached and I was wondering what would happen if one day Expo is no longer available or get shut down so then my app is not able to run bc it relies on expo.
Is it possible that I have my own javascript bundle locally or running on my server so I don't have to rely on expo at all. If so what changes are needed so my .apk file is not relying on expo but rather on my own bundle.js
The eject command doesn't depend on expo, so if one day expo stops working, you can detach your project from theirs and start building your own apk.

Can't test my app on IOS using Expo.io. Cannot find module hashAssetFiles

I’m new to expo.io and I’ve created a simple app using Expo XDE. I’m using a windows 10 PC and testing via QR with an IPhone 6S and a Galaxy S8.
The problem is that I can’t test my app on the iPhone because it throws an error saying “Cannot find module project route/node_modules/expo/tools/hashAssetFiles. Meanwhile, on the Galaxy S8 works perfectly!
Error image here.
Does anyone know how can I solve this problem? Thanks in advance!
It seems this occurs when you don't have expo installed as a dependency in your node_modules and package.json, you have the wrong version of a package installed, or you have it installed in the wrong section. Make sure your expo dependencies are under dependencies and not under dev-dependencies.
Reference: Github Issue

Categories

Resources