React native was working perfectly till today. But, Suddenly I'm facing a weird error. Whenever I try to load js from the react native android app. I'm getting the following messages.. Transforming progress bar is stopping exactly in 96% every time.
Let me know, If you need any extra information.
Thanks,
In my case, This was due to a package called MaterialReactNative. If there is some problem in the package, this will be stopped in transforming. If you want to know which package is making this problem. You can start react native in verbose mode.
react-native start -vvv
I hope that this will help few people who are facing the same issue.
Related
I've been working on a ios/android app with react native for the first time and am struggling with dependencies issues. Can someone help me understand what this error message means and how to fix it?
not enough rep to post the image itself
I'm getting the infamous Maximum Stack Call Size Exceeded error in Expo app.
I understand that it's caused by code that keeps calling itself, creating an infinite loop.
Does Expo or React Native provide more information about where this error is? I've already been through my code and didn't find anything. Something a bit more specific would be helpful in narrowing down the issue.
What's evn more interesting in this case is that I only get the error in the Expo Go app. When I run the app in Android Emulator, I don't get the error and the app works fine.
Any suggestions?
I found the culprit and it's totally unexpected.
I develop web front-end in React and mobile in React Native. One of the primary reasons is code sharing.
I have a file that contains all the action types I use in managing the state of my app. Technically not but kind of an enum file. They look like this:
export const SET_IS_AUTHENTICATED = 'SET_IS_AUTHENTICATED';
export const SET_USER_INFO = 'SET_USER_INFO';
In this file, I have exactly 486 action types and this is exactly what was creating the error.
I don't need all of these action types in my mobile app but I'd decided to keep things consistent and I thought this was totally harmless so I've been sharing this enum file in all my React and React Native apps.
Here are two interesting observations:
I just started developing with Expo. Prior to that I was using straight React Native -- created through React Native CLI and I NEVER got any errors for using this file.
Even more interesting is that the Android Emulator does NOT throw any errors in the same project. Only the Expo Go app throws this error.
This may even be by design and not necessarily an undesired side effect of the Expo Go app. Not sure. I'd love to know if others have had similar experiences with the Expo Go app.
This is probably not helpful, but when I upgraded from expo sdk 41 to 43 then I started getting this error. I made no code changes besides the upgrade and now when my app loads I get the error Unhandled promise rejection, [RangeError: Maximum call stack size exceeded.]. I get the error on expo go on both platforms
I am using RN version 0.60 and My app is stuck in white screen without getting any error
Try turning on debug mode. If it still exists,there is problem in your code or setup.
I was having an issue with gradle. After updating it to latest version everything working fine.
The bundles might be loading at that time. Have a look at your terminal any errors might be thrown there.
I was just coding away, when suddenly the debugger broke and every time I try to reload my app via Expo, cmd shows me the following error:
I am new to react native, hence clueless what might be wrong. Any ideas?
Thanks!
The issue was that remote JS debugging was activated via the developer menu on the phone. I must have accidentally tapped it when reloading the app.
I've been trying out React Native lately and I got everything setup right.
Im running my Android Virtual Device and my RN app is displaying and reloading just fine.
However, every after a certain amount of time, when i hit RR (refresh) i get this error:
The only way I can seem to recover from this is if I rerun React native command:
react-native run-android
After that, it's ok again..... until after a few minutes, I get that dreaded RED SCREEN OF DEATH again.
What could be causing this? Timeout of some sort?
TIA
There are some reasons for that.
You have problem on JS files you are using (you can see errors on
react packager)
You are closing the react packager terminal after run your app
It closes itself automatically with some terminal reasons
Do you get any error on react packager?