Recursive header expansion when using other libs such as Firebase

[ethanyuwang]

I installed AppCenter and CodePush as instructed. When I tried to compile I encountered this error:

Showing Recent Issues
Argument list too long: recursive header expansion failed at /Users/ethanwang/Github/reactnative/Glever_RNI/Glever/node_modules/appcenter/ios/../../../ios/Pods/React/node_modules/fsevents/node_modules/har-validator/lib/node6.

Enviroment:

"react-native": "0.53.0",
node: v8.9.4
cocoapods-1.4.0

I have looked up this error it seems like it was fixed on V1.20 (#209)

But I'm still experiencing the same error. How should I fix this?

[ElektrojungeAtWork]

Hi @ethanyuwang,

I'd like to help you with this. The title of this issue (still) suggests that you had this issue before? I couldn't find it here on Github, can you point me to it, please?

If this is a new issue, can you please provide more context?

• RN version
• Node version (It looks like you are using node 6)
• Cocoapods version
• When does the error happen?

[ethanyuwang]

@TroubleMakerBen Hi, thank you. I have just updated my issue.

[ethanyuwang]

Any updates on this?

[guperrot]

We released cocoapods 1.4.0 support only in our SDK version 1.3.0 and your issue is saying you are using cocoapods 1.4.0.

Can you try on our 1.3.0 SDK?

[guperrot]

Also we are not compatible with react native 0.53 at the moment. You will have to downgrade temporarily to 0.52 to be able to execute react-native link and then update react again after, sorry for the inconvenience

[BrijeshShiroya]

I had the same issue. I tried to install npm into another system. But still getting same issue. Can you please help me? What is the exact issue?

[guperrot]

What versions are you using for our SDK and Cocoapods and react-native.

[dilee716]

I'm having same issues
SDK: 1.3.0
Cocoapods: 1.4.0
react-native: 0.52.1

[guperrot]

The header search path for app center should not be recursive:

Do you have recursive on appcenter headers?

[dilee716]

they are not-recursive

[guperrot]

but is your error about recursive headers like in the first comment or is it another issue? Please share the exact error message.

[dilee716]

error is just like first comment.
Argument list too long: recursive header expansion failed at /Users/dominic/MyAwesomeApp/node_modules/appcenter-analytics/ios/../../../ios/Pods/React/Libraries.

[guperrot]

This is a really weird error since you don't use recursive header but complains about recursive, I cannot reproduce here. We will need you to share project sources so we can repro.

[dilee716]

There are some other headers that are recursive. The appcenter headers are not recursive.

[guperrot]

Do you need those to be recursive? Can you share sources please?

[ethanyuwang]

I'm not very sure if this was the fix since I have tried a lot of different things, but I don't have this error anymore.

Somehow there's another react folder in my pods then I deleted it and included this code in my Podfile:

  pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
  pod 'React', :path => '../node_modules/react-native'

Then when running pod install the pods won't install a react pod inside the Pods folder but instead, they look for the react folder in node_modules.

[guperrot]

@ethanyuwang I don't have a React directory in Pods folder though I don't have those lines either. Do you need React as a pod dependency? Anyway deleting React under Pods seems like the right thing to do, not sure about the Podfile part.

[ethanyuwang]

I think it was needed for react-native-firebase. I did notice pod install would install react-native 0.11 if I don't have that code in my Podfile when I tried to install appcenter

[guperrot]

Ok its indeed caused by https://github.com/invertase/react-native-firebase/blob/master/ios/RNFirebase.podspec#L18

[guperrot]

@dilee716 @BrijeshShiroya do you use other 3rd party libs depending on react as pods ? You can look for React in ios/Podfile.lock, if yes you can follow the steps described in #246 (comment) to work around the issue.

[dilee716]

yeah, currently using other 3rd party libs depending on react as pods. Messing around with it right now. thanks for checking in @guperrot

[thebradbain]

Has there been any update on this? Or is this workaround the solution still?

[guperrot]

Hi, right now the work around is still needed.

[dhei]

As a follow up, v1.5.1 is released today and this issue should be fixed.

Thanks.