Published App not Running

#1

Hi there,

I have published my app the Expo servers and am trying to run, but it fails to load (see screenshot below).

It runs fine locally on both simulator and device.

Thanks for your help.

Tim

App.json

{
  "expo": {
    "name": "Galley",
    "slug": "galley",
    "privacy": "unlisted",
    "icon": "./src/assets/icon.png",
    "sdkVersion": "19.0.0",
  }
}

Package.json

{
  "name": "pack_tech_mobile",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "babel-plugin-import": "^1.4.0",
    "jest-expo": "~1.0.1",
    "react-native-scripts": "0.0.31",
    "react-test-renderer": "^15.6.1"
  },
  "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
  "scripts": {
    "start": "react-native-scripts start",
    "eject": "react-native-scripts eject",
    "android": "react-native-scripts android",
    "ios": "react-native-scripts ios",
    "test": "node node_modules/jest/bin/jest.js --watch",
    "clean-start": "rm -rf node_modules && yarn install && rm -rf $TMPDIR/react* && npm start --reset-cache"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "antd-mobile": "^1.6.3",
    "babel-eslint": "^7.2.3",
    "enzyme": "^2.9.1",
    "eslint-config-airbnb": "^15.0.1",
    "eslint-config-airbnb-standard": "^1.2.6",
    "expo": "^19.0.0",
    "firebase": "^4.3.0",
    "moment": "^2.18.1",
    "nock": "^9.0.14",
    "prop-types": "^15.5.10",
    "react": "16.0.0-alpha.12",
    "react-dom": "^15.6.1",
    "react-native": "^0.46.0",
    "react-navigation": "^1.0.0-beta.11",
    "sinon": "^2.3.6",
    "underscore": "^1.8.3"
  }
}

0 Likes

#2

@timothyvoice There are a couple small differences between running your app locally and publishing it. In order to get a better debugging experience, when you are testing your app in the XDE, in the gear on the top left corner, uncheck Development Mode. This should be able to give you the same errors you are seeing when you publish.

Issues that could arise in the Published version that is not present in the local version could be due to variables like __DEV__, which is true when run locally, but false when published. If your app depends on such variables being set to a certain value, it may cause bugs down the road.

0 Likes

#3

@quinlanj That was exactly what was wrong.

I am using ant-design-mobile and it requires a babel plugin. Once I included that loader in the production settings of my .babelrc the app ran after being published.

Even more useful as your hint about XDE and taking it out of development mode.

Thanks for your help!

1 Like