HomeiOS Developmentios - React Native expo server getting closed with the error -...

ios – React Native expo server getting closed with the error – FATAL ERROR: Reached heap restrict Allocation failed – JavaScript heap out of reminiscence


I’ve a React native app in-built Expo, after I run the npx expo begin and run the app on Expo app on IOS I get the under error:
enter image description here

however the app does hold operating with out crashing. After utilizing the appliance for some time the server mechanically crashes and reveals the under error:
enter image description here

I solely see this behaviour whereas operating the app on IOS gadget, I’m not dealing with any points whereas operating the identical utility on Android gadget a effectively as android emulator.

The SDK model of my utility is 47 and my bundle.json is as under:

  "dependencies": {
"@expo-google-fonts/cormorant-upright": "^0.2.2",
"@expo-google-fonts/montserrat": "^0.2.2",
"@expo-google-fonts/righteous": "^0.2.2",
"@expo/html-elements": "^0.2.2",
"@react-native-async-storage/async-storage": "~1.17.3",
"@react-native-community/datetimepicker": "6.5.2",
"@react-native-community/netinfo": "9.3.5",
"@react-navigation/bottom-tabs": "^6.4.1",
"@react-navigation/native": "^6.0.8",
"@react-navigation/native-stack": "^6.5.2",
"@twotalltotems/react-native-otp-input": "1.3.7",
"axios": "^1.4.0",
"expo": "~47.0.6",
"expo-app-loading": "~2.1.1",
"expo-constants": "^14.0.2",
"expo-dev-client": "~2.0.1",
"expo-device": "~5.0.0",
"expo-firebase-recaptcha": "~2.3.1",
"expo-font": "~11.0.1",
"expo-google-app-auth": "~8.3.0",
"expo-haptics": "~12.0.1",
"expo-image-picker": "~14.0.2",
"expo-linear-gradient": "~12.0.1",
"expo-notifications": "~0.17.0",
"expo-permissions": "~14.0.0",
"expo-splash-screen": "~0.17.5",
"expo-status-bar": "~1.4.2",
"expo-updates": "~0.15.6",
"expo-web-browser": "~12.0.0",
"firebase": "9.6.11",
"second": "^2.29.4",
"pod-install": "^0.1.32",
"radio-buttons-react-native": "^1.0.4",
"react": "18.1.0",
"react-dom": "18.1.0",
"react-native": "0.70.8",
"react-native-animatable": "^1.3.3",
"react-native-deck-swiper": "^2.0.5",
"react-native-element-dropdown": "^2.5.0",
"react-native-gesture-handler": "^2.8.0",
"react-native-gifted-chat": "^1.0.4",
"react-native-loading-dots": "^1.3.2",
"react-native-modal-datetime-picker": "^13.1.2",
"react-native-paper": "^4.12.4",
"react-native-phone-number-input": "^2.1.0",
"react-native-range-slider-expo": "^1.4.3",
"react-native-safe-area-context": "^4.4.1",
"react-native-screens": "^3.18.2",
"react-native-shadow-2": "^7.0.6",
"react-native-size-matters": "^0.4.0",
"react-native-svg": "13.4.0",
"react-native-typing-animation": "^0.1.7",
"react-native-web": "~0.18.7",
"react-native-webview": "11.23.1",
"react-native-wheel-picker-expo": "^0.5.2",
"rn-progress-loader": "^1.0.8",
"uuid": "^8.3.2"
}

Any concept what may very well be inflicting this situation?

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments