diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index ea83a24f783..f0558b10c59 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -7,7 +7,7 @@ // iOS device are on the same Wi-Fi network. jsCodeLocation = [NSURL URLWithString:@"http://localhost:9381/index.ios.bundle"];
Permission settings prevent Watchman from loading. A recent update solves this, get a HEAD install of Watchman if you are experiencing this error.
If in the react-native init <project> phase you saw npm fail with "npm WARN locking Error: EACCES" then try the following:
It is possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. If you are having this issue, try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.
To see the exact error that is causing your build to fail, go into the Issues Navigator in the left sidebar.
If you are using CocoaPods, verify that you have added React along with the subspecs to the Podfile. For example, if you were using the <Text />, <Image /> and fetch() APIs, you would need to add these in your Podfile:
It is possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. If you are having this issue, try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.
To see the exact error that is causing your build to fail, go into the Issues Navigator in the left sidebar.
If you are using CocoaPods, verify that you have added React along with the subspecs to the Podfile. For example, if you were using the <Text />, <Image /> and fetch() APIs, you would need to add these in your Podfile: