none
Error installing npm vcremote - Failed at the node-ios-device@1.1.0 install script RRS feed

  • Question

  • I'm having issue installing the vcremote package from npm. I need this package to build native c++ library for my cross platform app.

    I followed the instruction from here https://docs.microsoft.com/en-us/visualstudio/cross-platform/install-and-configure-tools-to-build-using-ios. 

    output log from npm install:

    13904 verbose lifecycle node-ios-device@1.1.0~install: CWD: /usr/local/lib/node_modules/vcremote/node_modules/node-ios-device
    13905 silly lifecycle node-ios-device@1.1.0~install: Args: [ '-c', 'node-pre-gyp install --fallback-to-build' ]
    13906 silly lifecycle node-ios-device@1.1.0~install: Returned: code: 1  signal: null
    13907 info lifecycle node-ios-device@1.1.0~install: Failed to exec install script
    13908 verbose unlock done using /Users/<username>/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging
    13909 verbose stack Error: node-ios-device@1.1.0 install: `node-pre-gyp install --fallback-to-build`
    13909 verbose stack Exit status 1
    13909 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:280:16)
    13909 verbose stack     at emitTwo (events.js:125:13)
    13909 verbose stack     at EventEmitter.emit (events.js:213:7)
    13909 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
    13909 verbose stack     at emitTwo (events.js:125:13)
    13909 verbose stack     at ChildProcess.emit (events.js:213:7)
    13909 verbose stack     at maybeClose (internal/child_process.js:927:16)
    13909 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
    13910 verbose pkgid node-ios-device@1.1.0
    13911 verbose cwd /Users/<username>/dev/sandbox/vcremote
    13912 verbose Darwin 17.6.0
    13913 verbose argv "/usr/local/Cellar/node/8.6.0/bin/node" "/usr/local/bin/npm" "install" "-g" "--unsafe-perm" "vcremote"
    13914 verbose node v8.6.0
    13915 verbose npm  v5.5.1
    13916 error code ELIFECYCLE
    13917 error errno 1
    13918 error node-ios-device@1.1.0 install: `node-pre-gyp install --fallback-to-build`
    13918 error Exit status 1
    13919 error Failed at the node-ios-device@1.1.0 install script.
    13919 error This is probably not a problem with npm. There is likely additional logging output above.
    13920 verbose exit [ 1, true ]

    I also see this error in the npm console: 

    <style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #d53bd3; background-color: #000000} span.s1 {font-variant-ligatures: no-common-ligatures; color: #bfbfbf} span.s2 {font-variant-ligatures: no-common-ligatures; color: #49bc6f} span.s3 {font-variant-ligatures: no-common-ligatures; color: #990000} span.s4 {font-variant-ligatures: no-common-ligatures} span.s5 {font-variant-ligatures: no-common-ligatures; color: #00a600} </style>

    node-pre-gyp ERR! Tried to download(403): https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v1.1.0/node_ios_device-v1.1.0-node-v57-darwin-x64.tar.gz 

    node-pre-gyp ERR! Pre-built binaries not found for node-ios-device@1.1.0 and node@8.6.0 (node-v57 ABI) (falling back to source compile with node-gyp) 

    node-pre-gyp http 403 status code downloading tarball https://appc-node-binaries.s3.amazonaws.com/node-ios-device/v1.1.0/node_ios_device-v1.1.0-node-v57-darwin-x64.tar.gz 

    • Moved by Baron Bi Monday, July 9, 2018 8:31 AM Not related to c++ development
    Thursday, July 5, 2018 8:32 PM

All replies

  • Hi,

    thanks for posting here.

    This forum is about c++ code issues. For your case which is more related to NPM installation, I suggest you try this support forum below.

    https://www.npmjs.com/support

    Your understanding and cooperation will be grateful.

    Best Regards,

    Baron Bi


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, July 6, 2018 5:21 AM