All extension installations fail (WinXP)

[frgc]

WinXP SP3
sprint 36 experimental build 0.36.0-11506 (release 942505c)

"Installation failed.
Unknown internal error."

Using extension manager this is what I get immediately upon trying to install an extension. There is no network activity. There is no antivirus and I tried unblocking brackets in windows firewall.

[dangoor]

Medium priority to me to investigate.

[dangoor]

@frgc Is there anything in the console (select Show Developer Tools from the Debug menu)?

[damouk]

I have the same problem - and the same set up (WinXP Sp3, sprint 36) (I'm using this through a proxy, but Sprint 35 worked fine).

This is the only line output in Developer tools:
"Unknown installation error extensionManager domain is undefined"

[frgc]

Same, from Dev Tools

Unknown installation error extensionManager domain is undefined
/extensibility/Package.js:367

[dangoor]

@bchintx Is it possible that Node fails to start up on WinXP sp3 with the new binary module for file watching?

[bchintx]

@dangoor Ug. Something's definitely not working right. If I delete the installed 'fswatch_win.node' file, then launch Brackets and try to install an extension, the installation succeeds.

[Diex]

same behavior here... after deleting 'fswatch_win.node' file, installation succeeds.

[bchintx]

Updating title to reflect that this is Windows XP-specific.

[njx]

Marking for sprint 37

[le717]

There is an old XP tower sitting in the floor of the other room, perhaps I can get a chance to set up and try this out myself sometime this week.

[bchintx]

@JeffryBooher fixed this issue by disabling the native file watching node module on XP. See PR #7131

[telis93]

I am experiencing this issue in Windows 7 and developer tools fail to start and when I click Debug -> Restart Node I get a js alert saying "Failed to restart node: Cannot call method 'restartNode' of undefined"

[dangoor]

@telis93 Your issue is likely a different problem. Please file a new issue.

[peterflynn]

Removing FBNC tag since we've decided we want to use a slightly different fix for XP -- one that doesn't cause #6551 to reappear, but that disables watchers & caching (so XP will just behave like Sprint 35).

[peterflynn]

New fix ongoing in PR #7170

[peterflynn]

Setting back to FBNC so we can test tomorrow. We should also spin off a bug about getting watchers working in XP (ideally via @bchintx's native extension still).

[gillisig]

I am getting the same issue in windows 7. Dev tools displays the same as the others:

Unknown installation error extensionManager domain is undefined /extensibility/Package.js:367

[bchintx]

Created new Issue #7200 to track fixing native file watching on Windows XP.

@gillisig The extensionManager domain error is probably a new problem. Can you please file a new issue for this? Thanks.

Closing this issue as fixed with @JeffryBooher 's now-merged pull request.

[mcmanimie]

I'm seeing this issue also on Mac 10.9 running v44. I can't install any extensions.

"Unknown installation error extensionManager domain is undefined"

[redmunds]

@mcmanimie Please open a New Issue.

[mcmanimie]

@redmunds My bad. Here you go: #9625