Invalid argument while ejecting

$ expo diagnostics

  Expo CLI 3.21.10 environment info:
    System:
      OS: Windows 10 10.0.18363
    Binaries:
      Node: 12.17.0 - C:\Program Files\nodejs\node.EXE
      Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
    IDEs:
      Android Studio: Version  4.0.0.0 AI-193.6911.18.40.6514223
    npmPackages:
      expo: ~37.0.3 => 37.0.12
      react: ~16.9.0 => 16.9.0
      react-dom: ~16.9.0 => 16.9.0
      react-native: ~0.61.5 => 0.61.5
      react-native-web: ~0.11.7 => 0.11.7
      react-navigation: ^4.3.9 => 4.4.0

Trying to eject (expo eject) and it gives me this error:

  • Applying iOS configurationEINVAL: invalid argument, mkdir ‘D:\Projects\mobile_app\react_native\ios\D:\Projects\mobile_app\react_native\ios\TheNameOfMyApp’

And it looks like it trying to generate some necessary project files for ios, but I actually don’t need any ios files and I need only android configuration to be up and running.
Is it possible to eject only for android? Since I only need android ejected for debugging purposes.

I am having the same problem.

Applying iOS configurationEINVAL: invalid argument, mkdir ‘C:\Users\chris\Documents\MyApp\ios\C:\Users\chris\Documents\MyApp\ios\MyApp’

The path is doubled up for some reason.

Expo CLI 3.21.10 environment info:
System:
OS: Windows 10 10.0.18363
Binaries:
Node: 14.4.0 - C:\Program Files\nodejs\node.EXE
npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
Watchman: 4.9.4 - C:\Install\watchman\watchman.EXE
IDEs:
Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6514223
npmPackages:
expo: ~37.0.3 => 37.0.12
react: ~16.9.0 => 16.9.0
react-dom: ~16.9.0 => 16.9.0
react-native: ~0.61.5 => 0.61.5
react-native-web: ~0.11.7 => 0.11.7
react-navigation: ^4.4.0 => 4.4.0

at Object.mkdirSync (fs.js:940:3)
at createEntitlementsFile (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\node_modules\@expo\config\src\ios\Entitlements.ts:77:8)
at Object.getEntitlementsPath (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\node_modules\@expo\config\src\ios\Entitlements.ts:68:54)
at modifyEntitlementsPlistAsync (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\commands\apply\configureIOSProjectAsync.ts:59:49)
at configureIOSProjectAsync (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\commands\apply\configureIOSProjectAsync.ts:38:9)
at configureIOSStepAsync (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\commands\eject\Eject.ts:115:3)
at Object.ejectAsync (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\commands\eject\Eject.ts:60:3)
at action (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\commands\eject.ts:45:5)
at Command.<anonymous> (C:\Users\chris\AppData\Roaming\npm\node_modules\expo-cli\src\exp.ts:80:7)
1 Like

I suspect the bug, so waiting for the comment from the developers.

Opened an issue on the github: https://github.com/expo/expo/issues/8970