Stuck on SplashScreen after SDK update

Expo SDK
1

My app gets stuck on the splash screen after updating to SDK 31. If I reload it a few times it generally opens. I am not sure where the issue is. Any thoughts? This is happening on ios and android. Thanks for your time, Osha

2

Hey @digndirt,

Is this occurring in the Expo Client or as a standalone apk/ipa? Can you running the command expo start --no-dev --minify to reproduce the behavior and see if that sheds any light?

Cheers,

Adam

3

Hi Adam, thanks for your timely reply,

I am using the Expo Client, expo cli. I ran the command you suggested, I am not seeing any change in behavior, and no info.

4

This is my package .json. Using node 8.14.1

{
“main”: “node_modules/expo/AppEntry.js”,
“private”: true,
“dependencies”: {
“@expo/vector-icons”: “^8.0.0”,
“@redux-offline/redux-offline”: “^2.3.2”,
“@sentry/wizard”: “^0.10.2”,
“babel-preset-expo”: “^5.0.0”,
“buffer”: “^5.1.0”,
“expo”: “^31.0.4”,
“fetchival”: “^0.3.3”,
“haversine-js”: “^1.0.0”,
“native-base”: “2.8.2”,
“react”: “16.5.0”,
“react-native”: “https://github.com/expo/react-native/archive/sdk-31.0.1.tar.gz”,
“react-native-keyboard-aware-scroll-view”: “^0.5.0”,
“react-native-maps”: “^0.22.0”,
“react-native-maps-directions”: “^1.6.0”,
“react-native-modal-datetime-picker”: “^5.1.0”,
“react-native-sentry”: “^0.38.2”,
“react-native-tabs”: “^1.0.9”,
“react-navigation”: “^2.18.2”,
“react-redux”: “^5.0.7”,
“redux”: “^3.7.2”,
“redux-persist”: “^5.9.1”,
“redux-thunk”: “^2.2.0”,
“sentry-expo”: “~1.9.0”,
“uuid”: “^3.2.1”
},
“devDependencies”: {
“babel-plugin-module-resolver”: “^3.1.0”,
“jest-expo”: “^31.0.0”,
“reactotron-react-native”: “^1.14.0”
},
“scripts”: {
“test”: “node_modules/.bin/jest”
},
“jest”: {
“preset”: “jest-expo”
}
}

This warning came up today, I think it has to do with how I am loading assets:

[10:38:11] AppLoading threw an unexpected error when loading:
[10:38:11] g@http://127.0.0.1:19001/node_modules/expo/AppEntry.bundle?platform=ios&dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Foshafoster%2Fdev%2Fverisage%2Fdig-in-dirt-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js:98:380
[10:38:11] Dr@http://127.0.0.1:19001/node_modules/expo/AppEntry.bundle?platform=ios&dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Foshafoster%2Fdev%2Fverisage%2Fdig-in-dirt-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js:98:56505
[10:38:11] Or@http://127.0.0.1:19001/node_modules/expo/AppEntry.bundle?platform=ios&dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Foshafoster%2Fdev%2Fverisage%2Fdig-in-dirt-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js:98:57833
[10:38:11] jr@http://127.0.0.1:19001/node_modules/expo/AppEntry.bundle?platform=ios&dev=false&minify=true&hot=false&assetPlugin=%2FUsers%2Foshafoster%2Fdev%2Fverisage%2Fdig-in-dirt-app%2Fnode_modules%2Fexpo%2Ftools%2FhashAssetFiles.js:98:58238

An example of how I load assets:

const matchIcon = require(‘assets/bullseye.png’)

const blueHave = require(‘assets/blueHave.png’)

const blueLiked = require(‘assets/blueLiked.png’)

const logo = require(‘assets/logo.png’)

5

Hey. I am experiencing similar issues with version 31.0.4.

6

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