-
Notifications
You must be signed in to change notification settings - Fork 89
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
Does not work in OSX #57
Comments
Is it Chrome or Chromium? What OS do you use? |
Hi Pete, |
Chrome 38.0.2125.122 on OS X 10.9.5 |
I confirm this does not work on 39.0.2171.13 on OS X 10.9.5 |
This works on Yosemite + Chrome - Version 39.0.2171.95 ( see http://stackoverflow.com/a/24981514 )
replace line 39: #include <util.h> with #include "/usr/include/util.h"
|
Thanks for the details, @fungl164 . I tried following the instructions, but I get an error when installing '/tmp/pty.js' from the local directory. Any ideas how I can fix this? Error details: npm ERR! System Darwin 13.4.0 |
@msanand I just noticed something peculiar in I suspect it's a simple typo on the command. Give this a try |
I am using OSX: 10.10.1, Chrome: 40.0.2214.91, Node: 0.10.35 I am able to install devtools terminal. Note: pty.js now seems to be pointing to the correct path: I can run devtools-terminal after installing globally and adding the ID (which now gives me a "Chrome Native Messaging host application installed successfully"): However, I still see the welcome screen with the Native Messaging API messaging instead of a prompt. Is anyone else still getting that Announcement screen? |
thx @fungl164 this totally fixed the install. works great running chrome 40.0 on osx 10.10.1 |
Got this to work, finally. I assume there may have been an issue accessing the tool's default 8080 port from the browser to the socket server. I'll keep an eye on it, but otherwise, the plugin works like a charm. |
I followed @msanand's steps but unfortunately it's still not working for me on OSX 10.10.2, Chrome 41.0.2272.101. |
my devtool-terminal server is up, and it seems like it can establish an io handshake every time i try to connect
it will than create a new auth id
but the chrome terminal just says connection failed |
Having the same problem. @brschwar , did you do anything special to get it to work? |
I was able to get it working following the directions on this blog: Please note that you will need to install devtools-terminal globally:
Then run Next, access the terminal tab from the developer tools and ignore the NPAPI announcement. That's what got me at first - that announcement doesn't go away, instead click on the '...' preferences menu and login to a Remote Connection with the credentials: That worked for me - I could then use that panel in the same manner as I was able to before the Native Messaging update. Possible issues may come up if the default port of 8080 is already in use. |
Got it. I had sort-of figured that out yesterday, but was hoping I wouldn't have to log in each time. That seriously hampers the usability for me. :( |
Agreed! At least if that is how it worked originally, we wouldn't have gotten spoiled! Glad you were able to get it working. It's still very useful to be able to develop completely in the browser. |
Please help! -I installed the extension. And I get the following error:
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo. gyp ERR! build error
npm ERR! Darwin 14.4.0 npm ERR! [email protected] install: npm ERR! Please include the following file with any support request: npm ERR! enoent ENOENT, open '/tmp/pty.js' npm ERR! Please include the following file with any support request: |
Hi,
'devtools-terminal' worked perfectly fine until the move to Native Messaging API. Since then, I've never been able to get it working. I've installed and re-installed everything following the instructions, but all I see when I open terminal is the announcement and instructions to install it.
I really loved having devtools-terminal as it greatly enhanced my dev productivity. Please let me know if I'm missing something or how I can get it working again.
Thanks,
Anand
The text was updated successfully, but these errors were encountered: