eas build crash on open

Expo Application Services (EAS)
1

Hello, as I said in the title after I successfully execute eas build I open the app and it crashes in the splash screen, sentry can not debug it because the app has not opened. expo: build works great and also expo: go, I followed the expo guides without an answer.
Attaches my construction

eas json:
{

“cli”: {

"version": ">= 0.43.0"

},

“build”: {

"development": {

  "developmentClient": true,

  "distribution": "internal"

},

"preview": {

  "distribution": "internal"

},

"production": {}

},

“submit”: {

"production": {}

}

}

2
3

The guide has two tips or check in senetry where I have no report or in Xcode where it is written
exuupdatesAppController throwException

4

Ios or Android? managed o bare?

6

manged

7

Same problem

8

Hi

Try running in production mode:

expo start --no-dev --minify

That might give you more info.

Otherwise, check the device logs

Unforunately “it crashes at the splash screen” is not enough information to go on.

If the above don’t give you more information then maybe try this:

expo.fyi/manual-debugging

9

the production mode work fine, I try those things and no sulotion ,
maybe the Xcode log in expo page build can tell something?
I also atached packge json and
my packge json:
{

“scripts”: {

"start": "expo start",

"android": "expo start --android",

"ios": "expo start --ios",

"web": "expo start --web",

"eject": "expo eject"

},

“dependencies”: {

"@expo-google-fonts/inter": "^0.2.2",

"@firebase/firestore": "^2.4.0",

"@firebase/storage": "^0.6.2",

"@react-native-async-storage/async-storage": "~1.15.0",

"@react-native-community/datetimepicker": "4.0.0",

"@react-native-picker/picker": "2.2.1",

"@react-navigation/drawer": "^5.12.9",

"@sentry/react-native": "^3.4.2",

"async": "^3.2.1",

"axios": "^0.24.0",

"blob": "^0.1.0",

"cancelable-promise": "^4.2.1",

"expo": "^44.0.0",

"expo-app-loading": "~1.3.0",

"expo-application": "~4.0.1",

"expo-barcode-scanner": "~11.2.0",

"expo-chart-kit": "^1.2.4",

"expo-constants": "~13.0.1",

"expo-device": "~4.1.0",

"expo-firebase-core": "~4.1.0",

"expo-firebase-recaptcha": "~2.1.0",

"expo-font": "~10.0.4",

"expo-image-picker": "~12.0.1",

"expo-localization": "~12.0.0",

"expo-navigation-bar": "~1.1.1",

"expo-notifications": "~0.14.0",

"expo-permissions": "~13.1.0",

"expo-secure-store": "~11.1.0",

"expo-splash-screen": "~0.14.1",

"expo-status-bar": "~1.2.0",

"expo-system-ui": "~1.1.0",

"expo-updates": "~0.11.7",

"firebase": "8.2.3",

"firestore": "^1.1.6",

"i18n-js": "^3.8.0",

"react": "17.0.1",

"react-dom": "17.0.1",

"react-instantsearch-dom": "^6.12.1",

"react-native": "0.64.3",

"react-native-chart-kit": "^6.11.0",

"react-native-customized-image-picker": "^1.2.2",

"react-native-deck-swiper": "^2.0.5",

"react-native-device-info": "^8.4.9",

"react-native-gesture-handler": "~2.1.0",

"react-native-get-random-values": "~1.7.0",

"react-native-global-font": "^1.0.3",

"react-native-hide-show-password-input": "^1.2.0",

"react-native-i18n": "^2.0.15",

"react-native-internet-connection-alert": "^0.1.6",

"react-native-modal-datetime-picker": "^10.2.0",

"react-native-paper": "^4.9.2",

"react-native-passmeter": "0.0.5",

"react-native-password-strength-meter": "0.0.5",

"react-native-permissions": "^3.0.5",

"react-native-phone-call": "^1.0.9",

"react-native-progress": "^5.0.0",

"react-native-qrcode-scanner": "^1.5.4",

"react-native-qrcode-svg": "^6.1.1",

"react-native-reanimated": "~2.3.1",

"react-native-safe-area-context": "3.3.2",

"react-native-screens": "~3.10.1",

"react-native-svg": "12.1.1",

"react-native-web": "0.17.1",

"react-native-webview": "11.15.0",

"react-navigation": "^4.4.4",

"react-navigation-stack": "^2.10.4",

"react-navigation-tabs": "^2.11.1",

"sentry-expo": "^4.0.0",

"uuid": "^8.3.2"

},

“devDependencies”: {

"@babel/core": "^7.12.9",

"cross-env": "^7.0.3"

},

“private”: true

}

10

If you replace App.js with the default App.js from a newly created app does it still crash?
If not, try adding back code from your app a chunk at a time until the crash starts happening again.
That should narrow down where the problem is coming from.

1 Like
11

Thanks for the advice!! It was at the end InternetConnectionAlert that caused the problem

1 Like
12

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.