Argument list too long: recursive header expansion failed

I keep having this error no matter after installing react-native-firebase

Argument list too long: recursive header expansion failed at /var/www/upwork/bus5app/node_modules/react-native-fbsdk/ios/../../../ios/Pods/React/node_modules/vinyl-fs/node_modules/through2.

Also there is another issue as well:

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ActionSheetIOS
  Paths: /private/var/www/upwork/bus5app/ios/Pods/React/Libraries/ActionSheetIOS/ActionSheetIOS.js collides with /private/var/www/upwork/bus5app/node_modules/react-native/Libraries/ActionSheetIOS/ActionSheetIOS.js

(Please write your issue here along with the environment details below. Include any key files which will help us to debug, such as your Podfile and/or app/build.gradle file).

Environment

  1. Target Platform (e.g. iOS, Android): iOS
  2. Development Operating System (e.g. macOS Sierra, Windows 10): macOS Sierra
  3. Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant): Xcode
  4. React Native version (e.g. 0.45.1): ^0.46.2
  5. RNFirebase Version (e.g. 2.0.2): ^2.0.4
  6. “react-native-fbsdk”: “^0.6.0”

Author: Fantashit

5 thoughts on “Argument list too long: recursive header expansion failed

  1. I have updated the wording to read:

    If you do not already have React and Yoga installed as pods, then add Yoga and React to your `Podfile` as follows
    
  2. Same problem when I want to run my application via Xcode. Error message is:

    Argument list too long: recursive header expansion failed at /Users/bsevindi/Desktop/projects/aracqr/node_modules/react-native-firebase/ios/../../../ios/Pods/React/node_modules/yeoman-generator/node_modules/inquirer/lib.

    My development environment is:
    react-native-cli: 2.0.1
    react-native: 0.52.0
    react-native-firebase: ^3.2.2
    Xcode Version 9.2 (9C40b)
    macOS High Siearra 10.13.2 (17C205)

  3. My issue was that various pods were using different versions of React. I needed a unified reference. Auto-removing them in the podfile fixed this issue and others.

    target <yourTarget> do
     pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
     pod 'React', :path => '../node_modules/react-native', :subspecs => [
       'BatchedBridge', # Required For React Native 0.45.0+
       'Core',
       # Add any other subspecs you want to use in your project
     ]
    end
    
    # Remove React from projects 
    post_install do |installer|
      installer.pods_project.targets.each do |target|
        if target.name == "React"
          target.remove_from_project
        end
      end
    end
    
  4. I had the same issue and following resolved my issue.

    1. remove ios/Pods by rm -rf ios/Pods.
    2. remove Podfile.lock.
    3. remove lines in Podfile that you didn’t add but there is.
    4. pod install

    My problem is gone.

Comments are closed.

Argument list too long: recursive header expansion failed

I keep having this error no matter after installing react-native-firebase

Argument list too long: recursive header expansion failed at /var/www/upwork/bus5app/node_modules/react-native-fbsdk/ios/../../../ios/Pods/React/node_modules/vinyl-fs/node_modules/through2.

Also there is another issue as well:

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ActionSheetIOS
  Paths: /private/var/www/upwork/bus5app/ios/Pods/React/Libraries/ActionSheetIOS/ActionSheetIOS.js collides with /private/var/www/upwork/bus5app/node_modules/react-native/Libraries/ActionSheetIOS/ActionSheetIOS.js

(Please write your issue here along with the environment details below. Include any key files which will help us to debug, such as your Podfile and/or app/build.gradle file).

Environment

  1. Target Platform (e.g. iOS, Android): iOS
  2. Development Operating System (e.g. macOS Sierra, Windows 10): macOS Sierra
  3. Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant): Xcode
  4. React Native version (e.g. 0.45.1): ^0.46.2
  5. RNFirebase Version (e.g. 2.0.2): ^2.0.4
  6. “react-native-fbsdk”: “^0.6.0”

Author: Fantashit

5 thoughts on “Argument list too long: recursive header expansion failed

  1. I have updated the wording to read:

    If you do not already have React and Yoga installed as pods, then add Yoga and React to your `Podfile` as follows
    
  2. Same problem when I want to run my application via Xcode. Error message is:

    Argument list too long: recursive header expansion failed at /Users/bsevindi/Desktop/projects/aracqr/node_modules/react-native-firebase/ios/../../../ios/Pods/React/node_modules/yeoman-generator/node_modules/inquirer/lib.

    My development environment is:
    react-native-cli: 2.0.1
    react-native: 0.52.0
    react-native-firebase: ^3.2.2
    Xcode Version 9.2 (9C40b)
    macOS High Siearra 10.13.2 (17C205)

  3. My issue was that various pods were using different versions of React. I needed a unified reference. Auto-removing them in the podfile fixed this issue and others.

    target <yourTarget> do
     pod "yoga", :path => "../node_modules/react-native/ReactCommon/yoga"
     pod 'React', :path => '../node_modules/react-native', :subspecs => [
       'BatchedBridge', # Required For React Native 0.45.0+
       'Core',
       # Add any other subspecs you want to use in your project
     ]
    end
    
    # Remove React from projects 
    post_install do |installer|
      installer.pods_project.targets.each do |target|
        if target.name == "React"
          target.remove_from_project
        end
      end
    end
    
  4. I had the same issue and following resolved my issue.

    1. remove ios/Pods by rm -rf ios/Pods.
    2. remove Podfile.lock.
    3. remove lines in Podfile that you didn’t add but there is.
    4. pod install

    My problem is gone.

Comments are closed.

Argument list too long: recursive header expansion failed

I keep having this error no matter after installing react-native-firebase

Argument list too long: recursive header expansion failed at /var/www/upwork/bus5app/node_modules/react-native-fbsdk/ios/../../../ios/Pods/React/node_modules/vinyl-fs/node_modules/through2.

Also there is another issue as well:

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ActionSheetIOS
  Paths: /private/var/www/upwork/bus5app/ios/Pods/React/Libraries/ActionSheetIOS/ActionSheetIOS.js collides with /private/var/www/upwork/bus5app/node_modules/react-native/Libraries/ActionSheetIOS/ActionSheetIOS.js

(Please write your issue here along with the environment details below. Include any key files which will help us to debug, such as your Podfile and/or app/build.gradle file).

Environment

  1. Target Platform (e.g. iOS, Android): iOS
  2. Development Operating System (e.g. macOS Sierra, Windows 10): macOS Sierra
  3. Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant): Xcode
  4. React Native version (e.g. 0.45.1): ^0.46.2
  5. RNFirebase Version (e.g. 2.0.2): ^2.0.4
  6. “react-native-fbsdk”: “^0.6.0”

Author: Fantashit

3 thoughts on “Argument list too long: recursive header expansion failed

  1. Same problem when I want to run my application via Xcode. Error message is:

    Argument list too long: recursive header expansion failed at /Users/bsevindi/Desktop/projects/aracqr/node_modules/react-native-firebase/ios/../../../ios/Pods/React/node_modules/yeoman-generator/node_modules/inquirer/lib.

    My development environment is:
    react-native-cli: 2.0.1
    react-native: 0.52.0
    react-native-firebase: ^3.2.2
    Xcode Version 9.2 (9C40b)
    macOS High Siearra 10.13.2 (17C205)

  2. I had the same issue and following resolved my issue.

    1. remove ios/Pods by rm -rf ios/Pods.
    2. remove Podfile.lock.
    3. remove lines in Podfile that you didn’t add but there is.
    4. pod install

    My problem is gone.

Comments are closed.