iOS builds crash on Testflight when opened but not on emulator or when compiled onto device from xCode

🐛 Bug Report

Summary of Issue

Same as: https://forums.expo.io/t/after-migration-from-expokit-to-bare-the-new-build-crashes-on-testflight/40605/2

I’ve never experienced this until I moved to the bare workflow from ExpoKit. My build will work fine on emulator and also works fine compiled onto my phone through a USB cable. However when shipped through TestFlight the build instantly crashes and doesn’t even reach the splashscreen. Debug log shows the following thread crashing: expo.controller.AssetFilesQueue and you can find the full crash report here: https://pastebin.com/yMfLihni.

I don’t see any remarkable error codes in console when I attach to the device through a cable so console is of no use. This crash log / stack trace is the only hint that I have regarding what’s going on. I have a feeling this relates to expo-updates though and it specifically started happening when I enabled EXUpdatesLaunchWaitMs to 30000 in Expo.plist.

Expo updates is latest version.

Environment - output of expo diagnostics & the platform(s) you’re targeting

Expo CLI 3.22.3 environment info:
    System:
      OS: macOS 10.15.4
      Shell: 3.1.0 - /usr/local/bin/fish
    Binaries:
      Node: 14.4.0 - ~/.nvm/versions/node/v14.4.0/bin/node
      Yarn: 1.22.4 - ~/.yarn/bin/yarn
      npm: 6.14.5 - ~/.nvm/versions/node/v14.4.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.5 AI-191.8026.42.35.5900203
      Xcode: 11.6/11E708 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~38.0.8 => 38.0.8
      react: ~16.11.0 => 16.11.0
      react-dom: ~16.11.0 => 16.11.0
      react-native: ~0.62.2 => 0.62.2
      react-native-web: ~0.11.7 => 0.11.7
      react-navigation: ^4 => 4.4.0
    npmGlobalPackages:
      expo-cli: 3.22.3

[lc3t35]

@shamilovtim here it is :

I made some fix for expo-updates, @bugsnag/react-native and now I’m able to get this error in bugsnag :

TypeError · null is not an object (evaluating '_.releaseChannel')

I suspect a package using expo-constants (which is not available on bare) ? Bingo !

"@bugsnag/expo@^7.3.1":
  version "7.3.1"
  resolved "https://registry.yarnpkg.com/@bugsnag/expo/-/expo-7.3.1.tgz#d8322b2b7dc07621e82029ef3d25cbfb708fdc19"
  integrity sha512-WBiB5zkjN1g7x8nKi58xDBbWxXx0eL0C4YeEer3MTvfPmsnOHg4PNb9N4qFj9zneY1vW76qmznN9A/6N8H55yQ==
  dependencies:
    "@bugsnag/core" "^7.3.0"
    "@bugsnag/delivery-expo" "^7.3.0"
    "@bugsnag/plugin-browser-session" "^7.3.0"
    "@bugsnag/plugin-console-breadcrumbs" "^7.3.0"
    "@bugsnag/plugin-expo-app" "^7.3.0"
    "@bugsnag/plugin-expo-device" "^7.3.0"
    "@bugsnag/plugin-network-breadcrumbs" "^7.3.0"
    "@bugsnag/plugin-react" "^7.3.1"
    "@bugsnag/plugin-react-native-app-state-breadcrumbs" "^7.3.0"
    "@bugsnag/plugin-react-native-connectivity-breadcrumbs" "^7.3.0"
    "@bugsnag/plugin-react-native-global-error-handler" "^7.3.0"
    "@bugsnag/plugin-react-native-orientation-breadcrumbs" "^7.3.0"
    "@bugsnag/plugin-react-native-unhandled-rejection" "^7.3.0"
    bugsnag-build-reporter "^1.0.1"
    bugsnag-sourcemaps "^1.1.0"
    expo-constants "^6.0.0"

So I’ve update the package.json

"dependencies": {
    "@bugsnag/react-native": "^7.3.2",
    "@expo/vector-icons": "^10.2.0",
    "@microsoft/microsoft-graph-client": "^2.0.0",
    "@ptomasroos/react-native-multi-slider": "2.2.2",
    "@react-native-community/async-storage": "~1.11.0",
    "@react-native-community/datetimepicker": "2.4.0",
    "@react-native-community/masked-view": "0.1.10",
    "@react-native-community/netinfo": "5.9.2",
    "@react-native-firebase/analytics": "^7.3.1",
    "@react-native-firebase/app": "^8.2.0",
    "@react-native-firebase/messaging": "^7.4.2",
    "@react-navigation/compat": "^5.2.3",
    "@react-navigation/native": "^5.7.1",
    "@react-navigation/stack": "^5.7.1",
    "axios": "^0.19.2",
    "expo": "^38.0.9",
    "expo-ads-admob": "~8.2.1",
    "expo-asset": "~8.1.7",
    "expo-auth-session": "~1.4.0",
    "expo-calendar": "~8.2.1",
    "expo-cli": "^3.24.0",
    "expo-contacts": "~8.2.1",
    "expo-font": "~8.2.1",
    "expo-google-app-auth": "^8.1.2",
    "expo-linking": "^1.0.3",
    "expo-permissions": "~9.0.1",
    "expo-sms": "~8.2.1",
    "expo-splash-screen": "^0.3.1",
    "expo-status-bar": "^1.0.2",
    "expo-updates": "~0.2.8",
    "expo-web-browser": "~8.3.1",
    "firebase": "7.9.0",
    "i18next": "^19.6.3",
    "link-preview-js": "^2.0.4",
    "lodash": "4.17.19",
    "moment": "2.27.0",
    "normalizr": "3.6.0",
    "prop-types": "15.7.2",
    "react": "~16.11.0",
    "react-dom": "16.11.0",
    "react-i18next": "11.7.0",
    "react-native": "~0.62.2",
    "react-native-calendars": "^1.313.0",
    "react-native-device-info": "^5.6.1",
    "react-native-elements": "1.2.7",
    "react-native-gesture-handler": "~1.6.0",
    "react-native-iap": "4.5.2",
    "react-native-keyboard-aware-scroll-view": "0.9.1",
    "react-native-modal": "11.5.6",
    "react-native-modalize": "^2.0.5",
    "react-native-progress-bar-animated": "1.0.6",
    "react-native-reanimated": "~1.9.0",
    "react-native-safe-area-context": "~3.0.7",
    "react-native-screens": "~2.9.0",
    "react-native-snap-carousel": "3.9.1",
    "react-native-svg": "12.1.0",
    "react-native-swipe-list-view": "3.1.3",
    "react-native-unimodules": "~0.10.1",
    "react-native-web": "~0.11.7",
    "react-redux": "7.2.1",
    "redux": "4.0.5",
    "redux-form": "8.3.6",
    "redux-persist": "6.0.0",
    "redux-persist-expo-securestore": "2.0.0",
    "redux-thunk": "2.3.0"
  },

Problem solved for me.

[Thomasosho]

Check for syntax. Something as little as a key value could cause it to crash