I have a react-native app and I use Expo V49 to handle dependencies and release.
When I run my app over expo Go, it works perfectly, no problem at all. But when I make a TestFlight release over expo, the app crashes immediately, it does not open at all, just a splash is being visible for half of a second.
I tried to find something. The only thing I came across over MacOS’s Console is this:
error 18:24:03.164308+0200 SpringBoard Scene FBSceneManager/sceneID:app.letscape.www-default update failed: <NSError: 0x28505c120; domain: FBSceneErrorDomain; code: 1 (operation-failed); reason: "Scene update failed."> {
NSUnderlyingError = <NSError: 0x280e9c7b0; domain: BSServiceConnectionErrorDomain; code: 3 (OperationFailed); reason: "XPC error received on message reply handler">;
}
error 18:24:03.164525+0200 SpringBoard Scene FBSceneManager/sceneID:app.letscape.www-default update failed: <NSError: 0x281195740; domain: FBSceneErrorDomain; code: 1 (operation-failed); reason: "Scene update failed."> {
NSUnderlyingError = <NSError: 0x280e9c6f0; domain: BSServiceConnectionErrorDomain; code: 3 (OperationFailed); reason: "XPC error received on message reply handler">;
}
error 18:24:03.164994+0200 SpringBoard Scene FBSceneManager/sceneID:app.letscape.www-default update failed: <NSError: 0x28505c8d0; domain: FBSceneErrorDomain; code: 1 (operation-failed); reason: "Scene update failed."> {
NSUnderlyingError = <NSError: 0x280e9d440; domain: BSServiceConnectionErrorDomain; code: 3 (OperationFailed); reason: "XPC error received on message reply handler">;
}
Any ideas how I can approach to pinpoint the place of the problem exactly?
The crash report does not include logs somehow. I am kinda stucked.
My package.json includes these dependencies:
"@expo-google-fonts/inter": "^0.2.3",
"@expo/rudder-sdk-node": "^1.1.1",
"@expo/spawn-async": "^1.7.2",
"@expo/vector-icons": "^13.0.0",
"@expo/xcpretty": "^4.2.2",
"@miblanchard/react-native-slider": "^2.3.1",
"@react-native-masked-view/masked-view": "^0.2.9",
"@react-navigation/native": "^6.1.7",
"@react-navigation/stack": "^6.3.17",
"@reduxjs/toolkit": "^1.9.5",
"expo": "^49.0.6",
"expo-app-loading": "^2.1.1",
"expo-blur": "~12.4.1",
"expo-font": "~11.4.0",
"expo-status-bar": "~1.6.0",
"expo-updates": "~0.18.11",
"install": "^0.13.0",
"lottie-react-native": "5.1.6",
"react": "18.2.0",
"react-native": "0.72.3",
"react-native-dropdown-picker": "^5.4.6",
"react-native-dropdown-select-list": "^2.0.4",
"react-native-elements": "^3.4.3",
"react-native-gesture-handler": "~2.12.0",
"react-native-maps": "1.7.1",
"react-native-pager-view": "6.2.0",
"react-native-reanimated": "~3.3.0",
"react-native-safe-area-context": "4.6.3",
"react-native-screens": "~3.22.0",
"react-native-snap-carousel": "^4.0.0-beta.6",
"react-native-tab-view": "^3.5.1",
"react-native-webview": "13.2.2",
"react-redux": "^8.1.1"
Best
Ali
2
Answers
The problem was that I was using the lib: react-native-reanimated and this was the main reason that the app failed. I installed this lib to try out things but forgot to delete. Seems this lib needs further configs on babel etc. Since I did not do that, it failed I guess.
I deleted it and the app worked.
The error messages you’ve provided seem to indicate issues with the scene updates in your app, but the specific cause can be tricky to diagnose without more context. Here are some steps you can take to pinpoint the problem:
Check Expo SDK Compatibility: Ensure that all your dependencies and packages are compatible with the Expo SDK version (v49) you’re using. Sometimes, certain packages might not be fully compatible and could lead to runtime issues.
Check Native Module Versions: Some of your packages (like
react-native-mapsandlottie-react-native) involve native modules. Make sure that the versions of these native modules are compatible with each other and with the Expo SDK you’re using.Examine Code Changes: If the app works on Expo Go but crashes in a TestFlight release, there might be differences in code or configuration. Review any code changes, especially those related to native module linking, configuration files, or build settings.
Check Expo Updates: Ensure that your Expo client and the Expo SDK are up to date. Sometimes, updating the Expo client can help resolve certain compatibility issues.
Check Native Modules Configuration: Verify that any native modules you’re using are correctly configured in your app. If there’s a mismatch in native module versions or configurations, it can lead to crashes.
Review Xcode Console: When building your app, open Xcode and connect a device to see the console logs. This might provide more detailed error messages that can help you pinpoint the issue.
Reproduce the Issue Locally: If possible, try to reproduce the issue in a development environment. If you can reproduce it locally, you might get more detailed logs or error messages that can lead you to the source of the problem.
Examine Dependencies: Carefully review any recent updates or additions to your dependencies. Sometimes, a new package version can introduce incompatibility issues.
Expo Forum: The Expo Community Forums can be a helpful resource. Search or ask questions there to see if others have encountered similar issues.
React Native Debugger: Consider using the React Native Debugger to debug your app. It provides advanced debugging features that might help you identify the problem.
Expo’s GitHub: Check the Expo GitHub repository and the repositories of any specific Expo packages you’re using. Sometimes, known issues and solutions are discussed there.
Contact Expo Support: If you’ve tried everything and are still stuck, consider reaching out to Expo’s official support channels for guidance.
Remember to make changes cautiously and ideally test them in a controlled environment before deploying to production.