Iâm unable to reproduce this issue on OSX and v8.1.3, could you tell me which version of node youâre using ? Iâm so sorry youâre encountering this. Must be a total pain!
No, nothing like that, but I wouldnât rule out some kind of intermittent failure. The unfortunate thing is that now I seem to be in a spot where I canât retry - it fails almost immediately. Where do the files that get downloaded go? Could I delete those and try again?
So I did an npm uninstall of exp, and then reinstalled, but still saw the same issue.
I noticed that the first step (Downloading Project Files) completed almost instantaneously, leading me to believe that it wasnât actually downloading anything, but instead referring to some set of corrupted files it had downloaded the first time when it had a connection issue. Working off a hunch, I found a .expo directory in my home directory and deleted it. When I tried the command again, I had to re-login, but then it downloaded the files successfully and worked.
In other words, if someone else encounters this problem, they can run rm -rf ~/.expo ⌠I imagine thereâs a smaller set of files that could be removed, but I donât know the system well enough to say which.
Thanks for your help, I think Iâm good to go now!
Just in case it helps anybody finding this thread: I also ran into the âUnhandledPromiseRejectionWarningâ problem described above. I tried deleting the ~/.expo directory (without success), but downgrading npm to the suggested 4.6.1 did fix the problem for me.