I’ve encountered this a few times with 9.10.1. It feels pretty unstable to me. Have you checked the deployment logs? Have a look at the deployment/logs/native_packager_log text file, there may be a clue there. Things I’ve tried (not all at once) which worked in the past:
Hope this helps.
Cris
Thanks for your response. Definitely helped me.
Watchman is definitely causing an issue, but I am not sure if it the main reason.
[Error] jest-haste-map: Watchman crawl failed. Retrying once with node crawler.
[Error] Usually this happens when watchman isn't running. Create an empty `.watchmanconfig` file in your project's root folder or initialize a git or hg repository in your project.
I did what it suggested above, but then I got the following error and the native application was even more inaccessible than before:
[Error] Error: Watchman error: RootResolveError: unable to resolve root C:/Users/.../MxProject: failed to parse json from C:/Users/.../MxProject/.watchmanconfig: '[' or '{' expected near end of file. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.
[Error] C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\metro-hermes-compiler\src\emhermesc.js:81
[Error] throw ex;
[Error] ^
[Error] Error: RootResolveError: unable to resolve root C:/Users/.../MxProject: failed to parse json from C:/Users/.../MxProject/.watchmanconfig: '[' or '{' expected near end of file
[Error] at BunserBuf.<anonymous> (C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\fb-watchman\index.js:95:23)
[Error] at BunserBuf.emit (events.js:315:20)
[Error] at BunserBuf.process (C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\bser\index.js:292:10)
[Error] at C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\bser\index.js:247:12
[Error] at processTicksAndRejections (internal/process/task_queues.js:75:11)
[Error] Emitted 'error' event on WatchmanWatcher instance at:
[Error] at Client.<anonymous> (C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\jest-haste-map\build\lib\WatchmanWatcher.js:172:10)
[Error] at Client.emit (events.js:315:20)
[Error] at BunserBuf.<anonymous> (C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\fb-watchman\index.js:107:12)
[Error] at BunserBuf.emit (events.js:315:20)
[Error] at C:\Program Files\Mendix\9.6.7.35942\modeler\tools\node\node_modules\bser\index.js:249:12
[Error] at processTicksAndRejections (internal/process/task_queues.js:75:11) {
[Error] watchmanResponse: {
[Error] version: '4.9.4',
[Error] error: "RootResolveError: unable to resolve root C:/Users/.../MxProject: failed to parse json from C:/Users/.../MxProject/.watchmanconfig: '[' or '{' expected near end of file"
[Error] }
[Error] }
After I removed the .watchmanconfig file the application ran successfully.
But despite this, I can still not access the application. Watchman is also not running at all.
[Error] jest-haste-map: Watchman crawl failed. Retrying once with node crawler.
[Error] Usually this happens when watchman isn't running. Create an empty `.watchmanconfig` file in your project's root folder or initialize a git or hg repository in your project.
[Error] Error: Watchman error: query failed: synchronization failed: root dir was removed or is inaccessible. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.
I also cleared the deployment directory, and I can’t count the number of times I’ve restarted.
I’m also in contact with our IT department to check if the firewall is causing an issue.
Hi Brent,
I have also faced similar issue, and my issue was fixed by doing a small change in wifi properties. I just changed the network profile to private from public and this solved the issue.
Not sure whether this helps in your case, but please try
Thanks