How to debug Production app that crashes immediately?

Expo Application Services (EAS)
1

Hello there!

First time here.

I have an app that’s been working perfectly fine in Expo Go and simulator.

Once I built it using EAS build and submitted to app store, both the Android and iOS version of the app crashes immediately upon opening.

I couldn’t get sentry working somewhere along the same issue here : Unable to send test event to Sentry from React Native using Expo · Issue #294 · expo/sentry-expo · GitHub

Any help would be appreciated. Thanks!

eas-cli/2.1.0 darwin-arm64 node-v16.17.0

app.config.js

export default {
“name”: “Healthy Kitchen V2”,
“slug”: “healthy-kitchen-app-2”,
“version”: “2.0.20”,
“orientation”: “portrait”,
“icon”: “./app/assets/logo-square.png”,
“splash”: {
“image”: “./app/assets/healthykitchen.png”,
“resizeMode”: “cover”,
“backgroundColor”: “#F1ECE2”
},
“updates”: {
“fallbackToCacheTimeout”: 0,
“url”: “https://u.expo.dev/626661c7-a28a-484e-b41c-75339d83fd47”
},
“assetBundlePatterns”: [
“**/*”
],
“ios”: {
“supportsTablet”: true,
“bundleIdentifier”: “com.eatology.kitchenappv2”
},
“android”: {
“package”: “com.eatology.kitchenappv2”,
“versionCode”: 7,
“permissions”:
},
“extra”: {
“eas”: {
“projectId”: “626661c7-a28a-484e-b41c-75339d83fd47”
},
“web_api_key”: process.env.WEB_API_KEY
},
“runtimeVersion”: {
“policy”: “sdkVersion”
}
}

Packaing.json

{
“name”: “kitchenappv2”,
“version”: “2.0.19”,
“main”: “node_modules/expo/AppEntry.js”,
“scripts”: {
“start”: “expo start”,
“android”: “expo start --android”,
“ios”: “expo start --ios”,
“web”: “expo start --web”
},
“dependencies”: {
“@ react-native-community/datetimepicker”: “6.2.0”,
“@ react-navigation/bottom-tabs”: “^6.4.0”,
“@ react-navigation/native”: “^6.0.13”,
“@ react-navigation/native-stack”: “^6.9.1”,
“axios”: “^0.24.0”,
“expo”: “~46.0.16”,
“expo-constants”: “~13.2.4”,
“expo-secure-store”: “~11.3.0”,
“expo-status-bar”: “~1.4.0”,
“expo-updates”: “~0.14.6”,
“lottie-react-native”: “5.1.3”,
“moment”: “^2.29.3”,
“react”: “18.0.0”,
“react-dom”: “18.0.0”,
“react-native”: “0.69.6”,
“react-native-elements”: “^3.4.2”,
“react-native-new-snap-carousel”: “^3.9.3”,
“react-native-render-html”: “^6.3.4”,
“react-native-safe-area-context”: “4.3.1”,
“react-native-screens”: “~3.15.0”,
“react-native-switch-selector”: “^2.1.4”,
“react-native-webview”: “11.23.0”
},
“devDependencies”: {
“@babel/core”: “^7.12.9”,
“babel-preset-expo”: “^8.3.0”
},
“private”: true
}

2

Hi @jantzen

Start with this page: https://docs.expo.dev/workflow/debugging/#production-errors

in particular the part that says:

Hint: Sometimes, running your app in “production mode” locally will show errors that normally wouldn’t be thrown. You can run an app locally in production by running npx expo start --no-dev --minify. “–no-dev” tells the server not to be run in development mode, and “–minify” will minify your code the same way it is for production JavaScript bundles.

3

Thanks for your reply.

I’ve done this too. It runs perfectly fine.

4

Try the other stuff on that page as well.

Also, see if the device logs give you anything.

If that doesn’t help, try this: fyi/manual-debugging.md at main · expo/fyi · GitHub