From 5bde748c021a162f87d732f707fe48123bfa5342 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Sun, 22 Apr 2018 15:15:22 +0000 Subject: [PATCH] Deploy website Deploy website version based on cafba9412b71d2dd132f3b7f6ff19e1bf05070d5 --- docs/0.10/getting-started.html | 4 ++-- docs/0.10/troubleshooting.html | 2 ++ docs/0.11/getting-started.html | 4 ++-- docs/0.11/troubleshooting.html | 2 ++ docs/0.12/getting-started.html | 4 ++-- docs/0.12/troubleshooting.html | 2 ++ docs/0.13/getting-started.html | 4 ++-- docs/0.13/troubleshooting.html | 2 ++ docs/0.14/getting-started.html | 4 ++-- docs/0.14/troubleshooting.html | 2 ++ docs/0.15/getting-started.html | 4 ++-- docs/0.15/troubleshooting.html | 2 ++ docs/0.16/getting-started.html | 4 ++-- docs/0.16/troubleshooting.html | 2 ++ docs/0.17/getting-started.html | 4 ++-- docs/0.17/troubleshooting.html | 2 ++ docs/0.18/getting-started.html | 4 ++-- docs/0.18/troubleshooting.html | 2 ++ docs/0.19/getting-started.html | 4 ++-- docs/0.19/troubleshooting.html | 2 ++ docs/0.20/getting-started.html | 4 ++-- docs/0.20/troubleshooting.html | 2 ++ docs/0.21/getting-started.html | 4 ++-- docs/0.21/troubleshooting.html | 2 ++ docs/0.22/getting-started.html | 4 ++-- docs/0.22/troubleshooting.html | 2 ++ docs/0.23/getting-started.html | 4 ++-- docs/0.23/troubleshooting.html | 2 ++ docs/0.24/getting-started.html | 4 ++-- docs/0.24/troubleshooting.html | 2 ++ docs/0.25/getting-started.html | 4 ++-- docs/0.25/troubleshooting.html | 2 ++ docs/0.26/getting-started.html | 4 ++-- docs/0.26/troubleshooting.html | 2 ++ docs/0.27/getting-started.html | 4 ++-- docs/0.27/troubleshooting.html | 2 ++ docs/0.28/getting-started.html | 4 ++-- docs/0.28/troubleshooting.html | 2 ++ docs/0.29/getting-started.html | 4 ++-- docs/0.29/troubleshooting.html | 2 ++ docs/0.30/getting-started.html | 4 ++-- docs/0.30/troubleshooting.html | 2 ++ docs/0.31/getting-started.html | 4 ++-- docs/0.31/troubleshooting.html | 2 ++ docs/0.32/getting-started.html | 4 ++-- docs/0.32/troubleshooting.html | 2 ++ docs/0.33/getting-started.html | 4 ++-- docs/0.33/troubleshooting.html | 2 ++ docs/0.34/getting-started.html | 4 ++-- docs/0.34/troubleshooting.html | 2 ++ docs/0.35/getting-started.html | 4 ++-- docs/0.35/troubleshooting.html | 2 ++ docs/0.36/getting-started.html | 4 ++-- docs/0.36/troubleshooting.html | 2 ++ docs/0.37/getting-started.html | 4 ++-- docs/0.37/troubleshooting.html | 2 ++ docs/0.38/getting-started.html | 4 ++-- docs/0.38/troubleshooting.html | 2 ++ docs/0.39/getting-started.html | 4 ++-- docs/0.39/troubleshooting.html | 2 ++ docs/0.40/getting-started.html | 4 ++-- docs/0.40/troubleshooting.html | 2 ++ docs/0.41/getting-started.html | 4 ++-- docs/0.41/troubleshooting.html | 2 ++ docs/0.42/getting-started.html | 4 ++-- docs/0.42/troubleshooting.html | 2 ++ docs/0.43/getting-started.html | 4 ++-- docs/0.43/troubleshooting.html | 2 ++ docs/0.44/getting-started.html | 4 ++-- docs/0.44/troubleshooting.html | 2 ++ docs/0.45/getting-started.html | 4 ++-- docs/0.45/troubleshooting.html | 2 ++ docs/0.46/getting-started.html | 4 ++-- docs/0.46/troubleshooting.html | 2 ++ docs/0.47/getting-started.html | 4 ++-- docs/0.47/troubleshooting.html | 2 ++ docs/0.48/getting-started.html | 4 ++-- docs/0.48/troubleshooting.html | 2 ++ docs/0.49/getting-started.html | 4 ++-- docs/0.49/troubleshooting.html | 2 ++ docs/0.5/getting-started.html | 4 ++-- docs/0.5/troubleshooting.html | 2 ++ docs/0.50/getting-started.html | 4 ++-- docs/0.50/troubleshooting.html | 2 ++ docs/0.51/getting-started.html | 4 ++-- docs/0.51/troubleshooting.html | 2 ++ docs/0.52/getting-started.html | 4 ++-- docs/0.52/troubleshooting.html | 2 ++ docs/0.53/getting-started.html | 4 ++-- docs/0.53/troubleshooting.html | 2 ++ docs/0.54/getting-started.html | 4 ++-- docs/0.54/troubleshooting.html | 2 ++ docs/0.6/getting-started.html | 4 ++-- docs/0.6/troubleshooting.html | 2 ++ docs/0.7/getting-started.html | 4 ++-- docs/0.7/troubleshooting.html | 2 ++ docs/0.8/getting-started.html | 4 ++-- docs/0.8/troubleshooting.html | 2 ++ docs/0.9/getting-started.html | 4 ++-- docs/0.9/troubleshooting.html | 2 ++ docs/getting-started.html | 4 ++-- docs/next/getting-started.html | 4 ++-- docs/next/troubleshooting.html | 2 ++ docs/troubleshooting.html | 2 ++ 104 files changed, 208 insertions(+), 104 deletions(-) diff --git a/docs/0.10/getting-started.html b/docs/0.10/getting-started.html index 05da2ca4e00..8c3ce09add1 100644 --- a/docs/0.10/getting-started.html +++ b/docs/0.10/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.10/troubleshooting.html b/docs/0.10/troubleshooting.html index e7d1974bb4b..d17631425e7 100644 --- a/docs/0.10/troubleshooting.html +++ b/docs/0.10/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.11/getting-started.html b/docs/0.11/getting-started.html index ee49ebbd0ad..924455325ed 100644 --- a/docs/0.11/getting-started.html +++ b/docs/0.11/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.11/troubleshooting.html b/docs/0.11/troubleshooting.html index a62413388e7..cea75a1b6bd 100644 --- a/docs/0.11/troubleshooting.html +++ b/docs/0.11/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.12/getting-started.html b/docs/0.12/getting-started.html index 4da8dc6b940..ea8bf2157ab 100644 --- a/docs/0.12/getting-started.html +++ b/docs/0.12/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.12/troubleshooting.html b/docs/0.12/troubleshooting.html index 0d1cf818ccd..bd985ec1e2e 100644 --- a/docs/0.12/troubleshooting.html +++ b/docs/0.12/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.13/getting-started.html b/docs/0.13/getting-started.html index 7bdada85c32..9bf01544ef4 100644 --- a/docs/0.13/getting-started.html +++ b/docs/0.13/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.13/troubleshooting.html b/docs/0.13/troubleshooting.html index eddd0d84ae5..d0c9f39763f 100644 --- a/docs/0.13/troubleshooting.html +++ b/docs/0.13/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.14/getting-started.html b/docs/0.14/getting-started.html index 13cf26444d3..074a6512406 100644 --- a/docs/0.14/getting-started.html +++ b/docs/0.14/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.14/troubleshooting.html b/docs/0.14/troubleshooting.html index 94e1a4fc5c1..6909bd88617 100644 --- a/docs/0.14/troubleshooting.html +++ b/docs/0.14/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.15/getting-started.html b/docs/0.15/getting-started.html index ef59acf7784..833529b7568 100644 --- a/docs/0.15/getting-started.html +++ b/docs/0.15/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.15/troubleshooting.html b/docs/0.15/troubleshooting.html index 32fbff37fda..29c811c2463 100644 --- a/docs/0.15/troubleshooting.html +++ b/docs/0.15/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.16/getting-started.html b/docs/0.16/getting-started.html index 37e5e69995b..97c8972e965 100644 --- a/docs/0.16/getting-started.html +++ b/docs/0.16/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.16/troubleshooting.html b/docs/0.16/troubleshooting.html index 876fe6d166a..73dafeb3f1b 100644 --- a/docs/0.16/troubleshooting.html +++ b/docs/0.16/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.17/getting-started.html b/docs/0.17/getting-started.html index dfebcc0daf8..2d6cd13015e 100644 --- a/docs/0.17/getting-started.html +++ b/docs/0.17/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.17/troubleshooting.html b/docs/0.17/troubleshooting.html index 963427ac4f5..1572d2ce796 100644 --- a/docs/0.17/troubleshooting.html +++ b/docs/0.17/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.18/getting-started.html b/docs/0.18/getting-started.html index d1230bdfc9c..42f08ed9a96 100644 --- a/docs/0.18/getting-started.html +++ b/docs/0.18/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.18/troubleshooting.html b/docs/0.18/troubleshooting.html index ead449dd6fe..e03ba7e495e 100644 --- a/docs/0.18/troubleshooting.html +++ b/docs/0.18/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.19/getting-started.html b/docs/0.19/getting-started.html index 40a3136b20e..feee2a58195 100644 --- a/docs/0.19/getting-started.html +++ b/docs/0.19/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.19/troubleshooting.html b/docs/0.19/troubleshooting.html index 3c922dab3e0..6f4b4f820fc 100644 --- a/docs/0.19/troubleshooting.html +++ b/docs/0.19/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.20/getting-started.html b/docs/0.20/getting-started.html index a4f731fc165..1e8899b66b5 100644 --- a/docs/0.20/getting-started.html +++ b/docs/0.20/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.20/troubleshooting.html b/docs/0.20/troubleshooting.html index 4f7ff6a3725..5f9d8fbacf6 100644 --- a/docs/0.20/troubleshooting.html +++ b/docs/0.20/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.21/getting-started.html b/docs/0.21/getting-started.html index c86616425fe..20527d3712f 100644 --- a/docs/0.21/getting-started.html +++ b/docs/0.21/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.21/troubleshooting.html b/docs/0.21/troubleshooting.html index b545f3df2b3..43eea8719f6 100644 --- a/docs/0.21/troubleshooting.html +++ b/docs/0.21/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.22/getting-started.html b/docs/0.22/getting-started.html index 6e1b6ef108a..e9b97ab078c 100644 --- a/docs/0.22/getting-started.html +++ b/docs/0.22/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.22/troubleshooting.html b/docs/0.22/troubleshooting.html index 620e849e26d..3a4e09e9362 100644 --- a/docs/0.22/troubleshooting.html +++ b/docs/0.22/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.23/getting-started.html b/docs/0.23/getting-started.html index e0e6d849714..ac94377764f 100644 --- a/docs/0.23/getting-started.html +++ b/docs/0.23/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.23/troubleshooting.html b/docs/0.23/troubleshooting.html index 046e2fffd74..8252183e9bc 100644 --- a/docs/0.23/troubleshooting.html +++ b/docs/0.23/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.24/getting-started.html b/docs/0.24/getting-started.html index 74a82244507..6056e2b5fba 100644 --- a/docs/0.24/getting-started.html +++ b/docs/0.24/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.24/troubleshooting.html b/docs/0.24/troubleshooting.html index 5d5ad36f802..72b98499a1d 100644 --- a/docs/0.24/troubleshooting.html +++ b/docs/0.24/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.25/getting-started.html b/docs/0.25/getting-started.html index 834b1b5040f..4f09e3d266c 100644 --- a/docs/0.25/getting-started.html +++ b/docs/0.25/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.25/troubleshooting.html b/docs/0.25/troubleshooting.html index d0b9155c0d5..0a55d9f4782 100644 --- a/docs/0.25/troubleshooting.html +++ b/docs/0.25/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.26/getting-started.html b/docs/0.26/getting-started.html index 3debfee0f59..6744e18e495 100644 --- a/docs/0.26/getting-started.html +++ b/docs/0.26/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.26/troubleshooting.html b/docs/0.26/troubleshooting.html index 51225e27f2f..52b7bb60116 100644 --- a/docs/0.26/troubleshooting.html +++ b/docs/0.26/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.27/getting-started.html b/docs/0.27/getting-started.html index f1a83d7faeb..658d6dfe0f0 100644 --- a/docs/0.27/getting-started.html +++ b/docs/0.27/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.27/troubleshooting.html b/docs/0.27/troubleshooting.html index 5bf38a62c51..36eb7c1a12c 100644 --- a/docs/0.27/troubleshooting.html +++ b/docs/0.27/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.28/getting-started.html b/docs/0.28/getting-started.html index ecbf73e0aa7..3d715c5fcac 100644 --- a/docs/0.28/getting-started.html +++ b/docs/0.28/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.28/troubleshooting.html b/docs/0.28/troubleshooting.html index 991cf63f6c6..6343998ca8b 100644 --- a/docs/0.28/troubleshooting.html +++ b/docs/0.28/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.29/getting-started.html b/docs/0.29/getting-started.html index 158215a3564..705496a31d3 100644 --- a/docs/0.29/getting-started.html +++ b/docs/0.29/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.29/troubleshooting.html b/docs/0.29/troubleshooting.html index 068074d323e..51eeda70e28 100644 --- a/docs/0.29/troubleshooting.html +++ b/docs/0.29/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.30/getting-started.html b/docs/0.30/getting-started.html index a09a5afba7d..0ad5de6d1cd 100644 --- a/docs/0.30/getting-started.html +++ b/docs/0.30/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.30/troubleshooting.html b/docs/0.30/troubleshooting.html index 96aa3f1d126..f74b8d104fb 100644 --- a/docs/0.30/troubleshooting.html +++ b/docs/0.30/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.31/getting-started.html b/docs/0.31/getting-started.html index 45fb4df4d43..107b2583bf3 100644 --- a/docs/0.31/getting-started.html +++ b/docs/0.31/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.31/troubleshooting.html b/docs/0.31/troubleshooting.html index 52971007cac..afe2eb0aba2 100644 --- a/docs/0.31/troubleshooting.html +++ b/docs/0.31/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.32/getting-started.html b/docs/0.32/getting-started.html index 1f31560de6c..987f4439eb9 100644 --- a/docs/0.32/getting-started.html +++ b/docs/0.32/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.32/troubleshooting.html b/docs/0.32/troubleshooting.html index be59072660a..e5dc2dbf581 100644 --- a/docs/0.32/troubleshooting.html +++ b/docs/0.32/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.33/getting-started.html b/docs/0.33/getting-started.html index fe76139cc47..82e1c43c266 100644 --- a/docs/0.33/getting-started.html +++ b/docs/0.33/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.33/troubleshooting.html b/docs/0.33/troubleshooting.html index 0a3ab82ff2a..60bd5e56791 100644 --- a/docs/0.33/troubleshooting.html +++ b/docs/0.33/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.34/getting-started.html b/docs/0.34/getting-started.html index da0d921e594..d0314de7509 100644 --- a/docs/0.34/getting-started.html +++ b/docs/0.34/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.34/troubleshooting.html b/docs/0.34/troubleshooting.html index 094d5d6bb3a..d372a916cba 100644 --- a/docs/0.34/troubleshooting.html +++ b/docs/0.34/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.35/getting-started.html b/docs/0.35/getting-started.html index ccc385dd80d..a9d1a8e2c49 100644 --- a/docs/0.35/getting-started.html +++ b/docs/0.35/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.35/troubleshooting.html b/docs/0.35/troubleshooting.html index 228d5ff2cd5..8cc6d137273 100644 --- a/docs/0.35/troubleshooting.html +++ b/docs/0.35/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.36/getting-started.html b/docs/0.36/getting-started.html index 2bb025ce9ef..e8fa9a2815f 100644 --- a/docs/0.36/getting-started.html +++ b/docs/0.36/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.36/troubleshooting.html b/docs/0.36/troubleshooting.html index a67246c012c..8d7c7665a51 100644 --- a/docs/0.36/troubleshooting.html +++ b/docs/0.36/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.37/getting-started.html b/docs/0.37/getting-started.html index 688a7be5e7f..ca8fabd1b60 100644 --- a/docs/0.37/getting-started.html +++ b/docs/0.37/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.37/troubleshooting.html b/docs/0.37/troubleshooting.html index 9858514327e..ec2984c46ea 100644 --- a/docs/0.37/troubleshooting.html +++ b/docs/0.37/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.38/getting-started.html b/docs/0.38/getting-started.html index cf646223020..2d4bebb97f9 100644 --- a/docs/0.38/getting-started.html +++ b/docs/0.38/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.38/troubleshooting.html b/docs/0.38/troubleshooting.html index d4aebf88a48..97f687a87b7 100644 --- a/docs/0.38/troubleshooting.html +++ b/docs/0.38/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.39/getting-started.html b/docs/0.39/getting-started.html index e4a590b86d0..49900d45129 100644 --- a/docs/0.39/getting-started.html +++ b/docs/0.39/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.39/troubleshooting.html b/docs/0.39/troubleshooting.html index 2776af4d9e6..b2dd02792d8 100644 --- a/docs/0.39/troubleshooting.html +++ b/docs/0.39/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.40/getting-started.html b/docs/0.40/getting-started.html index e5ae15ddc82..bbfae7902ce 100644 --- a/docs/0.40/getting-started.html +++ b/docs/0.40/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.40/troubleshooting.html b/docs/0.40/troubleshooting.html index e07cd002dd3..4ab45cd3af1 100644 --- a/docs/0.40/troubleshooting.html +++ b/docs/0.40/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.41/getting-started.html b/docs/0.41/getting-started.html index 5d6328a9329..59de93836e0 100644 --- a/docs/0.41/getting-started.html +++ b/docs/0.41/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.41/troubleshooting.html b/docs/0.41/troubleshooting.html index 1467c0ffcc6..043334c5322 100644 --- a/docs/0.41/troubleshooting.html +++ b/docs/0.41/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.42/getting-started.html b/docs/0.42/getting-started.html index 947fce2f46d..6d4a8468e91 100644 --- a/docs/0.42/getting-started.html +++ b/docs/0.42/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.42/troubleshooting.html b/docs/0.42/troubleshooting.html index 69d4ea2f52b..617a9cc6c85 100644 --- a/docs/0.42/troubleshooting.html +++ b/docs/0.42/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.43/getting-started.html b/docs/0.43/getting-started.html index d7cccd0495b..26d089e835f 100644 --- a/docs/0.43/getting-started.html +++ b/docs/0.43/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.43/troubleshooting.html b/docs/0.43/troubleshooting.html index 06cfadf07c8..be0710ac9d3 100644 --- a/docs/0.43/troubleshooting.html +++ b/docs/0.43/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.44/getting-started.html b/docs/0.44/getting-started.html index b984f2bd880..cd1e72bdddf 100644 --- a/docs/0.44/getting-started.html +++ b/docs/0.44/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.44/troubleshooting.html b/docs/0.44/troubleshooting.html index c156784507a..4e807ca6ddf 100644 --- a/docs/0.44/troubleshooting.html +++ b/docs/0.44/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.45/getting-started.html b/docs/0.45/getting-started.html index f9fda799729..85914e8a915 100644 --- a/docs/0.45/getting-started.html +++ b/docs/0.45/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.45/troubleshooting.html b/docs/0.45/troubleshooting.html index e0b309847c8..d442fcb17aa 100644 --- a/docs/0.45/troubleshooting.html +++ b/docs/0.45/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.46/getting-started.html b/docs/0.46/getting-started.html index 6b079ad4cf8..3fb412a4c0f 100644 --- a/docs/0.46/getting-started.html +++ b/docs/0.46/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.46/troubleshooting.html b/docs/0.46/troubleshooting.html index 50c8733b6bc..9077086dd5e 100644 --- a/docs/0.46/troubleshooting.html +++ b/docs/0.46/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.47/getting-started.html b/docs/0.47/getting-started.html index 5ff04587cb9..51412b7d8ba 100644 --- a/docs/0.47/getting-started.html +++ b/docs/0.47/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.47/troubleshooting.html b/docs/0.47/troubleshooting.html index 9d58f65c4ff..dc58118f36c 100644 --- a/docs/0.47/troubleshooting.html +++ b/docs/0.47/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.48/getting-started.html b/docs/0.48/getting-started.html index dc7164c9250..2f88b263c35 100644 --- a/docs/0.48/getting-started.html +++ b/docs/0.48/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.48/troubleshooting.html b/docs/0.48/troubleshooting.html index cfb4635eb32..a458aebca7b 100644 --- a/docs/0.48/troubleshooting.html +++ b/docs/0.48/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.49/getting-started.html b/docs/0.49/getting-started.html index 4abc3c08d2a..10a75d3a6a4 100644 --- a/docs/0.49/getting-started.html +++ b/docs/0.49/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.49/troubleshooting.html b/docs/0.49/troubleshooting.html index 8bd27131294..dde4e118ca2 100644 --- a/docs/0.49/troubleshooting.html +++ b/docs/0.49/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.5/getting-started.html b/docs/0.5/getting-started.html index d3194d902bb..1622d03e65a 100644 --- a/docs/0.5/getting-started.html +++ b/docs/0.5/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.5/troubleshooting.html b/docs/0.5/troubleshooting.html index c6d23d8422b..d845b90b6ef 100644 --- a/docs/0.5/troubleshooting.html +++ b/docs/0.5/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.50/getting-started.html b/docs/0.50/getting-started.html index 4e04e4eb969..258b4452f36 100644 --- a/docs/0.50/getting-started.html +++ b/docs/0.50/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.50/troubleshooting.html b/docs/0.50/troubleshooting.html index 97fcc6733e9..2473a963654 100644 --- a/docs/0.50/troubleshooting.html +++ b/docs/0.50/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.51/getting-started.html b/docs/0.51/getting-started.html index 6fe7abbc936..545341750c2 100644 --- a/docs/0.51/getting-started.html +++ b/docs/0.51/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.51/troubleshooting.html b/docs/0.51/troubleshooting.html index 77f7d3851da..52e811b6352 100644 --- a/docs/0.51/troubleshooting.html +++ b/docs/0.51/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.52/getting-started.html b/docs/0.52/getting-started.html index e4cfd2549d9..b7e78ffe8c1 100644 --- a/docs/0.52/getting-started.html +++ b/docs/0.52/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.52/troubleshooting.html b/docs/0.52/troubleshooting.html index beda205da88..f7c80c1dcbd 100644 --- a/docs/0.52/troubleshooting.html +++ b/docs/0.52/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.53/getting-started.html b/docs/0.53/getting-started.html index 30e44d54fc3..56a224377e2 100644 --- a/docs/0.53/getting-started.html +++ b/docs/0.53/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.53/troubleshooting.html b/docs/0.53/troubleshooting.html index 5995a4c28f8..6a08cd04334 100644 --- a/docs/0.53/troubleshooting.html +++ b/docs/0.53/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.54/getting-started.html b/docs/0.54/getting-started.html index a151db61b0e..9e9ca091bd8 100644 --- a/docs/0.54/getting-started.html +++ b/docs/0.54/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.54/troubleshooting.html b/docs/0.54/troubleshooting.html index 40e6f9e2413..d37f6754b3e 100644 --- a/docs/0.54/troubleshooting.html +++ b/docs/0.54/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.6/getting-started.html b/docs/0.6/getting-started.html index 8591b52b63a..0597fc2469c 100644 --- a/docs/0.6/getting-started.html +++ b/docs/0.6/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.6/troubleshooting.html b/docs/0.6/troubleshooting.html index dcf1bdc52b3..87a940c745e 100644 --- a/docs/0.6/troubleshooting.html +++ b/docs/0.6/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.7/getting-started.html b/docs/0.7/getting-started.html index 6cb830f58d0..772e6fef661 100644 --- a/docs/0.7/getting-started.html +++ b/docs/0.7/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.7/troubleshooting.html b/docs/0.7/troubleshooting.html index 675eb39221d..5d8979ec4ce 100644 --- a/docs/0.7/troubleshooting.html +++ b/docs/0.7/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.8/getting-started.html b/docs/0.8/getting-started.html index 2baf4a8483e..69907fb23bf 100644 --- a/docs/0.8/getting-started.html +++ b/docs/0.8/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.8/troubleshooting.html b/docs/0.8/troubleshooting.html index e2e96b0a5c6..378c1d7081d 100644 --- a/docs/0.8/troubleshooting.html +++ b/docs/0.8/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/0.9/getting-started.html b/docs/0.9/getting-started.html index 7386313d28c..1459782180c 100644 --- a/docs/0.9/getting-started.html +++ b/docs/0.9/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/0.9/troubleshooting.html b/docs/0.9/troubleshooting.html index c20969d9100..7e782b46b9d 100644 --- a/docs/0.9/troubleshooting.html +++ b/docs/0.9/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/getting-started.html b/docs/getting-started.html index 38988b0800a..f636b2f872b 100644 --- a/docs/getting-started.html +++ b/docs/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/next/getting-started.html b/docs/next/getting-started.html index 2a91e7ffb80..c3fe7c215fa 100644 --- a/docs/next/getting-started.html +++ b/docs/next/getting-started.html @@ -334,13 +334,13 @@

Install HAXM

-

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, click on "Install HAXM" or follow these instructions to set it up, then go back to the AVD Manager.

AVD List

Install HAXM

-

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

+

If you don't have HAXM installed, follow these instructions to set it up, then go back to the AVD Manager.

AVD List

diff --git a/docs/next/troubleshooting.html b/docs/next/troubleshooting.html index d56a3294079..6fd58f235cb 100644 --- a/docs/next/troubleshooting.html +++ b/docs/next/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html index af475a02b03..3240661f2c7 100644 --- a/docs/troubleshooting.html +++ b/docs/troubleshooting.html @@ -36,6 +36,8 @@ sudo chown -R $USER / ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

+

React Native does not compile when being used as a CocoaPod

+

There is a CocoaPods plugin called cocoapods-fix-react-native which handles any potential post-fixing of the source code due to differences when using a dependency manager.

Argument list too long: recursive header expansion failed

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.