-
Notifications
You must be signed in to change notification settings - Fork 0
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
[CLOSED] Unable to install/update extensions on Mac 10.9 / v44 #8578
Comments
The same to LinuxMint 17(KDE),but all right at Ubuntu 14.04 32bit |
|
As noted, in my testing I deleted all my extensions and even trashed the Brackets folder under Application support, rebooted, then reinstalled. No dice. One thing that could be an issue is that at one point I installed (and then uninstalled) Adobe Edge Code. |
Ahh, sorry, I missed the disabling of extensions. The installation/removal of Edge Code should not have an impact on this. Were there any other errors in the dev tools? ("File watchers went offline!", perhaps?) |
Me too having the same issue with Brackets v0.45 and Mac OSX 10.9. I started using Brackets yesterday, and couldn't install any of the extensions. Console logs the error "Unknown installation error extensionManager domain is undefined", and nothing else. |
FWIW - I was able to install (most) plugins manually (Beautify failed, as did the Extension Ranker). |
It sounds to me like there's no reason that the Brackets-node process would be having trouble, which leads me back to this from your original description:
In Brackets, Node runs in a separate process (Brackets-node). That process listens on a random port (at least, I think it's random). On my machine right now, I see it listening on 56560. If Brackets-node is unable to listen on that port or Brackets is unable to connect to that port, then you'd see an error of the sort you're seeing. Assuming you're using the standard OS X Firewall, make sure you've allowed Brackets-node to accept incoming connections. I'm guessing that's what you did based on the quote above, but I wanted to double check because that's the best explanation I have for what you're seeing. |
|
|
|
For me, as soon as I started up the firewall, there was a prompt asking me whether I should allow Brackets-node to accept incoming connections. Ahh, I see a difference. I was running from master and not a release. I just fired up a release build and did not get prompted at all. That's probably because of the "Automatically allow signed software..." setting. Do you have that turned on? |
I do have that turned on, yes. |
Ha, well, it's magically working all of a sudden. I literally have no idea why. I made no substantive changes to my computer in the past week short of rebooting a few times. |
Hmm... That is mighty odd. I'll go ahead and close this now, then. Reopen it if it stops working again. (Also note that if you do ever run Brackets from a git clone you may need to update the firewall permissions) |
It broke for me. Steps that led to it borking:
|
I think I have the same issue on Mint 17. I even did a purge and deleted the .config/Brackets directory. As soon as I use Brackets 1.1, extension installation is broken. I got the following log: Download the React DevTools for a better development experience: http://fb.me/react-devtools /thirdparty/react.js:4356 is there anything I could try to investigate further? |
Wednesday Oct 22, 2014 at 02:18 GMT
Originally opened as adobe/brackets#9625
I was able to pop dev tools and the error is:
"Unknown installation error extensionManager domain is undefined"
I've ensured that brackets was included in the firewall exceptions list, moved all extensions into the disabled folder, and even deleted the entire Brackets directory and reinstalled. No dice.
The text was updated successfully, but these errors were encountered: