I am using a machine that we have successfully built with before but it has been a while. So I have updated expo-cli and tested the project. It works with Expo on my iPad and the published version works as well. Now I am trying expo build:ios
and I get the following:
>expo build:ios
There is a new version of expo-cli available (2.6.10).
You are currently using expo-cli 2.6.5
Run `npm install -g expo-cli` to get the latest version
[20:38:17] Making sure project is set up correctly...
[20:38:19] Your project looks good!
[20:38:19] Checking if current build exists...
[20:38:19] No currently active or previous builds for this project.
[20:38:19]
Does not seem like WSL enabled on this machine. Download from the Windows app
store a distribution of Linux, then in an admin powershell, please run:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
and run the new Linux installation at least once
? How would you like to upload your credentials?
I will provide all the credentials and files needed, Expo does limited validation
We need your Apple ID/password to ensure the correct teamID and appID
Note: Expo does not keep your Apple ID or your Apple password.
? What's your Apple ID? <appleID>
? Password? [hidden]
[20:38:41] Validating Credentials...
Error: spawn C:\Windows\system32\bash.exe ENOENT
at _errnoException (util.js:992:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
at onErrorNT (internal/child_process.js:372:16)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
This happens with expo-cli versions 2.6.10, 2.6.11, and now 2.6.5 after seeing some people having success after rolling back. Should I rollback further?
I have WSL enabled and Ubuntu installed. I have run Ubuntu and it works. I have uninstalled and reinstalled Ubuntu, and then created a user again. I have run Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
and I get the following. It is already enabled as far as I can tell.
Path :
Online : True
RestartNeeded : False
Why is it not able to find my WSL? gcm bash.exe
returns the correct path and bash.exe -c ‘uname’
gives me Linux. I believe everything is normal here.