更新firebase-admin后的EACCES错误

Question

我刚刚更新了firebase管理员，当我尝试访问我的firebase函数代码时，在运行firebase服务之后，我会得到EACCES错误。我提到在更新之前，代码运行良好。

我尝试重新安装节点模块，重新安装firebase和firebase管理，将serve命令作为admin运行，并在我的package.json文件中添加"engines"：{“节点”："8.15.0“}

完全错误：

i  functions: Beginning execution of "api"
!  Default "firebase-admin" instance created!
>  events.js:183
>        throw er; // Unhandled 'error' event
>        ^
> 
>  Error: listen EACCES C:\Users\Berce\AppData\Local\Temp\firebase_emulator_invocation_2608.sock
>      at Server.setupListenHandle [as _listen2] (net.js:1343:19)
>      at listenInCluster (net.js:1401:12)
>      at Server.listen (net.js:1496:5)
>      at Function.listen (C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\node_modules\express\lib\application.js:618:24)
>      at Promise (C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:359:46)
>      at new Promise (<anonymous>)
>      at C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:332:15
>      at Generator.next (<anonymous>)
>      at C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:7:71
>      at new Promise (<anonymous>)
>      at __awaiter (C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:3:12)
>      at ProcessHTTPS (C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:329:12)
>      at C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:523:23
>      at Generator.next (<anonymous>)
>      at fulfilled (C:\Program Files (x86)\Nodist\bin\node_modules\firebase-tools\lib\emulator\functionsEmulatorRuntime.js:4:58)
>      at <anonymous>
>      at process._tickCallback (internal/process/next_tick.js:189:7)
>      at Function.Module.runMain (module.js:696:11)
>      at startup (bootstrap_node.js:204:16)
>      at bootstrap_node.js:625:3

Answer 1

多亏了这些评论，我发现这个问题已经被火力小组发现了。在windows上复制，并且没有已知的修复方法。所以现在我不得不后退。

谢谢!