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

Not able to connect via both Native Messaging API & Web Socket on Mac Mavericks #49

Open
mudassir0909 opened this issue Jul 17, 2014 · 5 comments

Comments

@mudassir0909
Copy link

Native Messaging API

OS: Mavericks (using zsh)
Google Chrome: Version 36.0.1985.125

$ which node
/usr/local/bin/node

$ node -v
v0.10.28

$ npm install -g devtools-terminal

> pty.js@0.2.4 install /usr/local/lib/node_modules/devtools-terminal/node_modules/pty.js
> node-gyp rebuild

  CXX(target) Release/obj.target/pty/src/unix/pty.o
  SOLINK_MODULE(target) Release/pty.node
  SOLINK_MODULE(target) Release/pty.node: Finished

> ws@0.4.31 install /usr/local/lib/node_modules/devtools-terminal/node_modules/socket.io/node_modules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished

> ws@0.4.31 install /usr/local/lib/node_modules/devtools-terminal/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
/usr/local/bin/devtools-terminal -> /usr/local/lib/node_modules/devtools-terminal/bin/devtools-terminal
devtools-terminal@0.1.2 /usr/local/lib/node_modules/devtools-terminal
├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── pty.js@0.2.4 (extend@1.2.1, nan@0.7.0)
└── socket.io@1.0.6 (debug@0.7.4, has-binary-data@0.1.1, socket.io-parser@2.2.0, socket.io-adapter@0.2.0, engine.io@1.3.1, socket.io-client@1.0.6)





$ sudo devtools-terminal --install --id=leakmhneaibbdapdoienlkifomjceknl
Password:
Chrome Native Messaging host application installed successfully

$ cat com.dfilimonov.devtoolsterminal.json
{
  "name": "com.dfilimonov.devtoolsterminal",
  "description": "Devtools Terminal",
  "path": "/usr/local/lib/node_modules/devtools-terminal/bin/nm-host.sh",
  "type": "stdio",
  "allowed_origins": [
    "chrome-extension://leakmhneaibbdapdoienlkifomjceknl/"
  ]
}%


$ ls -l nm-host.sh
-rwxr-xr-x  1 mudassir  staff  184 Jan 16 21:02 nm-host.sh

After all this I see the following (Also tried restarting the chrome )
ss

Connecting via Websocket server

$ devtools-terminal

/usr/local/lib/node_modules/devtools-terminal/bin/devtools-terminal:280
  io.configure(function (){
     ^
TypeError: Object #<Server> has no method 'configure'
    at Object.<anonymous> (/usr/local/lib/node_modules/devtools-terminal/bin/devtools-terminal:280:6)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:906:3
@alarie
Copy link

alarie commented Jul 18, 2014

I have exactly the same problem.

@brennebeck
Copy link

Also verified here. @petethepig anything we can do to assist here? It looks like lots of people have been having issues getting the extension running.

@arthurvr
Copy link

I have that issue too.

@kvonspiczak
Copy link

Same here.. Worked on my previous computer. Now since I got a new one, it won't let me install it again.

@nmrt
Copy link

nmrt commented Aug 23, 2014

If you use Chromium, run sudo devtools-terminal --install --chromium.

Found out by checking out https://raw.githubusercontent.com/petethepig/devtools-terminal/master/backend/bin/devtools-terminal.

Now it works! 😃

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

6 participants