Expo

Documentation

Common Development Errors

Here you will find a list of errors that are commonly encountered by developers using Expo. For each error, the first bullet provides an explanation for why the error occurs and the second bullet contains debugging suggestions. If there is an error you think belongs here, we welcome and encourage you to create a PR!

  • Either you do not have expo-cli installed or it is not properly configured in your $PATH.
  • Install expo-cli if you have not already. Otherwise, check how to set your $PATH based on your OS.

  • An error is preventing the connection to your local development server.
  • Run rm -rf .expo to clear your local state. Check for firewalls or proxies affecting the network you are currently connected to.

  • An error in your code is preventing the JavaScript bundle from being executed on startup.
  • Try running expo start --no-dev --minify to reproduce the production JS bundle locally. If possible, connect your device and access the device logs via Android Studio or Xcode. Device logs contain much more detailed stacktraces and information. Check to see if you have any changes or errors in your Babel configuration.

  • Either you do not have git installed or it is not properly configured in your $PATH.
  • Install git if you have not already. Otherwise, check how to set it in your $PATH based on your OS.

  • The SDK version you are running has been deprecated and is no longer supported.
  • Upgrade your project to a supported SDK version. If you are using a supported version and see this message, you'll need to update your Expo client app. If you experience this error in a standalone app, make sure you have published a JS bundle for the specific SDK version and release channel for the given binary via expo publish.