Skip to content
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

Unable to run app on React Native Android device while using wml #11

Open
andrekovac opened this issue Feb 26, 2017 · 4 comments
Open

Comments

@andrekovac
Copy link

I used wml to keep a React Native module I'm writing in sync with the version in the node_modules folder of my Example App. Starting the React Native development server worked fine. Also building the app for Android worked successfully. I just always got the error the development server returned response error code :404 (see this issue) and after restarting wml several times my laptop began spinning like crazy and eventually nothing would work anymore...

Could it have to do with the fact that my wml destination folder is a subfolder of my source folder?

@dutzi
Copy link
Contributor

dutzi commented Feb 26, 2017

Most probably this is the reason.

Changes in the src folder trigger WML's copy method, since the dst folder lives inside the src folder it should loop infinitely.

@andrekovac
Copy link
Author

andrekovac commented Feb 26, 2017

Moving the folder out and trying it again after a restart of the computer gives me (libuv) kqueue(): Too many open files in system when I try to to start the React Native packager in the Example App which contains the destination folder in its node_modules folder.

I also got this error before at some point..

@dutzi
Copy link
Contributor

dutzi commented Feb 26, 2017

I've never seen that before...

Do you get this error only when WML is running? If so can you share the contents of .watchmanconfig from your src folder?

Try deleting your node_modules folder from your dst folder and running npm install and wml start again (not likely but it could be residue from previous runs of Wml...)

@andrekovac
Copy link
Author

Good hint with the .watchmanconfig. It got overwritten and was empty. Reverted that. But my machine doesn't stop to be churn and get another weird error when trying to run the packager while WML is running..

child_process.js:513
    throw err;
    ^

I'll give it up for now because I have to get something done for my project. I'll get back to it later. But thanks a lot for your fast reply and help @dutzi !

motornyi pushed a commit to motornyi/wml that referenced this issue Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants