Skip to content
This repository has been archived by the owner on Jul 9, 2019. It is now read-only.

Troubleshooting

Meredith Rouse edited this page Mar 30, 2017 · 4 revisions

Hopefully you never have to use these steps, but if you get stuck trying to fix something here are some things you can try.

Yarn

Yarn should be a pretty solid tool but you could occasionally have issues. According to the official yarn docs it should be installed via homebrew if you're on MacOS.

Troubleshooting Steps
  1. yarn cache clean. Since yarn pulls packages from local cache first before re-downloading anything you might need to clear that cache.
  2. Because of the nature of yarn and how it functions, you could run the same install/run commands using NPM in order to ensure yarn isn't the source of the problem.
  3. Reinstall Yarn. Homebrew makes this easy. brew uninstall yarn && brew install yarn

NVM and NPM

NVM is a node version manager to ease the process of adding/testing version of Node is your project. NPM is installed with each version of Node inside NVM.

Troubleshooting Steps
  1. Both projects have a cache store that can be cleared. nvm cache clear and npm cache clear respectively.
  2. NVM has tools to reinstall packages, the downside is that you can't run the command while running the version of Node you are trying to correct. Temporarily switch to a different version and run nvm reinstall-packages <version> to reinstall all global packages that are currently in the version of Node.
  3. Reinstall the version of node you are trying to run.
  4. Reinstall NVM entirely. (Probably not the source of your problem though).

React and React Native

This project is written in React/React Native because we ❤️ Javascript and React. That being said there could be issues with both frameworks.

Troubleshooting Steps
  1. Remove the build directory based on the platform you are running. ie ios/build or android/build to ensure that no old data is being added.
  2. If you're getting the red screen of death that doesn't point directly to code in the project then most likely there is a problem with a package (babel) that could be causing issues between platforms (native vs web). Try removing presets from the .babelrc one by one until you see a change.
  3. You can start the React Native server without cache with ./node_modules/react-native/packager/packager.sh start --resetCache.

Xcode

Xcode is for iOS development and can be alot to manage.

Troubleshooting Steps
  1. Delete Preference Files ~/Library/Preferences/com.apple.dt.****
  2. You can use Fastlane to remove and install simulators: fastlane snapshot reset_simulators
  3. Reinstall Xcode (This isn't an exhaustive list but we should add more steps when appropriate)