P0 issue: accessing .auth() throwing error that util.promisify() was not receiving a function! breaks several of our applications

[REQUIRED] Step 2: Describe your environment

• Operating System version: Linux (Heroku Dyno)
• Firebase SDK version: ^9.0.0
• Firebase Product: auth
• Node.js version: 10.6.0
• NPM version: 6.7.0

[REQUIRED] Step 3: Describe the problem:

My Heroku Server randomly started crashing recently and wont boot back up (even though it works perfectly fine locally). If I comment out const firebaseAdmin = firebaseApp.auth() , then it deploys with no crash, but as soon as I comment it back in, it crashes. This is breaking our applications and so this has become a P0 issue for us. Any help would be greatly appreciated. I will post screenshots of the error and the line of code I commented out that fixed the error. Thank you!

Steps to reproduce:

Deploy a heroku server and import the firebase-admin sdk and call the .auth() method with the same node and npm env. This issue has arisen within the past week, I’m not sure exactly when it started.

Relevant Code:

Error:

Fixed by commenting out:

I’ve gone through and tested it several times over, and consistently this ^ is the line of code causing it to crash.

Again this is NOT happening locally but for some reason only on a deployed heroku dyno instance.

Any help on this would be SUPER appreciated because it is currently breaking several of our apps

our firebaseApp firebase configuration has been working perfectly up until around last week and the error does not get thrown until .auth() is called so Im inclined to believe we have everything set up properly, unless something has changed recently about how it should all be setup configuration wise

[pfinazzo]

I downgraded my firebase-admin package to 8.4.0 and it works, so hopefully that can help narrow it down! Something deployed between 8.4.0 and now is definitely the source of the issue!

[lahirumaramba]

Updated the Node.js requirement in our package.json. The changes are now released with Admin SDK v9.9.0. @pfinazzo: Thank you for letting us know about this issue! Upgrading your node environment to 10.13.0 or higher should fix this. Please let us know if you run into further issues. Thanks!