Error : Argument list too long:recursive header expansion failed at /Applications/Adobe Acrobat 8 Professional/Adobe Acrobat Professional.app/

Can Any one tell why this error occur and how to resolve it

Check Dependencies

Argument list too long: recursive header expansion fail开发者_开发问答ed at /Applications/Adobe Acrobat 8 Professional/Adobe Acrobat Professional.app/Contents/Plug-ins/Comments.acroplugin/Contents/MacOS.

in my case the error was empty variable in "Header Search Paths" field (in project information) with recursion enabled.

This lead to pass value "/**" to a tool.

I'll share another scenario where you can have the same error.

I had the same problem in my case was related with the Derived Data. After clean the Derived Data folder the problem disappeared.

I just removed all entries under framework search paths. It works fine, in some other cases you may need to enable always search user paths flag to true.

In my case, deleting the build folder worked.

rm -rf ios/build

In the Project build settings Framework Search Paths I replaced:

/Users/My.Name/Documents/My-Project/**

with

/Users/My.Name/Documents/My-Project/

A different solution for me. I am using a static lib in my XCode project. In XCode preferences > Source trees I set up the lib as follows:

Setting Name: MY_IPHONE_LIB

Display Name: MY_IPHONE_LIB

Path: ../../MyIphoneLib

Then in the project and target build options User Header Search Paths I add recursive path to $(MY_IPHONE_LIB) this shows as ../../MyIphoneLib** in the build settings

My problem was I had a trailing space after the path in project trees so instead of "../../MyIphoneLib" I had entered "../../MyIphoneLib "

So this all looked fine in the settings but I got the 'argument list too long' error for a completely unrelated file!. Removing the trailing space fixed it.

the only thing to remove is search path from project information this solves my problem

I solved by revising Framework SearchPaths in .xcodeproj to

$(PROJECT_DIR)/../../../ios/Pods.

For future folks ... I faced this issue for a different reason.

Just check in your Project Settings that Build System is set to New Build System (Default)

Happy Coding

If you are using react native and run into this error, this helped me:

I had to use react-native unlink xxx to unlink the library i was trying to add which caused this error to occur (funny enough the error was about a different library not the one i just added)

After unlinking i followed the steps the library explained in its readme on how to add it manually without using the react native link, then it was happy after that.

Saw on reddit that a lot of people been complaining that react-native link breaks quite often and causes problems like this