3

Does anyone know what causes this problem? I already  deinstalled all mendix versions and also node.js When I press “Run Locally” in Studio Pro the responsive works fine, but for Native it finally leads into this error. I also tried to replace files form another machine where it is working. I don't know what else I can try. Mendix version 8.11.0   C:\Program Files\Mendix\8.11.0.1311\modeler\tools\node\node.exe "C:\Program Files\Mendix\8.11.0.1311\modeler\tools\node\node_modules\react-native\local-cli\cli.js" start --port "8083" --config "C:\Users\<username>\Documents\Mendix\TrackTrace-main\deployment\native\metro.config.json"  warn Failed to chmod xsel: EPERM: operation not permitted, chmod 'C:\Program Files\Mendix\8.11.0.1311\modeler\tools\node\node_modules\react-native\node_modules\@react-native-community\cli\build\commands\server\external\xsel' ┌──────────────────────────────────────────────────────────────────────────────┐ │                                                                              â”‚ │  Running Metro Bundler on port 8083.                                         │ │                                                                              â”‚ │  Keep Metro running while developing on any JS projects. Feel free to        â”‚ │  close this tab and run your own Metro instance if you prefer.               │ │                                                                              â”‚ │  https://github.com/facebook/react-native                                    â”‚ │                                                                              â”‚ └──────────────────────────────────────────────────────────────────────────────┘ Looking for JS files in    C:\Users\<username>\Documents\Mendix\TrackTrace-main\deployment\native    C:/Users/<username>/Documents/Mendix/TrackTrace-main/theme    C:/Users/<username>/Documents/Mendix/TrackTrace-main/javascriptsource    C:/Program Files/Mendix/8.11.0.1311/modeler/tools/node/node_modules  2020-07-27T09:35:48,905: [cli] unable to talk to your watchman on \\.\pipe\watchman-<username>! (No such file or directory) Watchman:  watchman --no-pretty get-sockname returned with exit code=1, signal=null, stderr= 2020-07-27T09:35:48,905: [cli] unable to talk to your watchman on \\.\pipe\watchman-<username>! (No such file or directory)

asked 2020-07-27

1 answers