-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spaces in the project path cause run-windows to fail #865
Comments
I'm struggling to come up with a good solution for this. I've searched for a few minutes for how to manage paths with spaces in them when invoking powershell from cmd but so far have come up empty handed. Is it possible to just not do this in a path with spaces ;-). If you have any specific suggestions for this, or have a few minutes to commit to this, would be great to get a PR. I've tried:
None of these things work. |
Oh yeah, no worries. I've already fixed the path in my project. Just thought I'd report the bug when I stumbled upon it. But yeah I'll give it a try myself as well and if I get something I'll let you know :) |
I still have this problem, how so? What can I do to fix this istantly and then wait for the maintainer to fix it? |
solution to this issue is to remove any special characters or spaces from your paths structure, my main folder was named DESKTOP APP so i changed it to DESKTOPAPP and rerun the app and it worked fine... you can also read my blog for detailed explanation of the errors i went through https://medium.com/@olabisiajoseh/setting-up-a-react-native-desktop-app-in-5-minutes-d06718838caa |
After executing
react-native run-windows
Powershell commands fail if there are spaces in the project path.I’ve tracked the offending lines to this file:
https://github.com/ReactWindows/react-native-windows/blob/9896aaa35b2da8ea1cbf941feb549c60c79569f7/local-cli/runWindows/utils/deploy.js
Lines 20, 83, 86, 89 and 92
Here's the initial error you get in the "untouched" state of the code :
When commenting out the faulty powershell commands everything runs fine.
The text was updated successfully, but these errors were encountered: