verifyIdToken in Modular Admin Node.js SDK

[SantiMA10]

Hi!

First of all thanks to the Firebase team, the new modular approach looks really nice.

I'm allowing my users to sign in with Twitch following the guidance of this Instagram example and it worked fine with the previous SDK version.

Once I completed the update to the new modular approach. I'm starting to get an auth/argument-error when I try to verify the id token in the backend. I have no idea of what is happening, any idea? Do I need to update the firebase version to 9.X? Let me know if I can give you more information.

Versions:

firebase: 8.4.2
firebase-admin: 9.100.0-alpha.0
node: 14.16.1

[hiranya911]

Do you have a complete error message or a stack trace to share? The auth/argument-error is just the error code portion of a larger error object.

[SantiMA10]

Here it is the complete error I get in the terminal

RangeError [ERR_HTTP_INVALID_STATUS_CODE]: Invalid status code: auth/argument-error
    at ServerResponse.writeHead (_http_server.js:255:11)
    at ServerResponse.writeHead (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/compiled/compression/index.js:1:155483)
    at ServerResponse._implicitHeader (_http_server.js:246:8)
    at ServerResponse.end (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/compiled/compression/index.js:1:141485)
    at onerror (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next-connect/lib/index.js:6:7)
    at /Users/santi/Projects/github/SantiMA10/ligths/node_modules/next-connect/lib/index.js:19:16
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async apiResolver (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/api-utils.js:8:1)
    at async DevServer.handleApiRequest (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/next-server.js:67:462)
    at async Object.fn (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/next-server.js:59:492)
    at async Router.execute (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/router.js:25:67)
    at async DevServer.run (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/next-server.js:69:1042)
    at async DevServer.handleRequest (/Users/santi/Projects/github/SantiMA10/ligths/node_modules/next/dist/next-server/server/next-server.js:34:504) {
  code: 'ERR_HTTP_INVALID_STATUS_CODE'
}

[hiranya911]

Thanks @SantiMA10. This looks like an error thrown by an express middleware (or something similar). My guess is you have code that's attempting to set the error code of a FirebaseError as the HTTP status code, which is causing the middleware to throw, and the original FirebaseError is lost in the process. We won't be able to debug the original error until this issue is addressed. If you can share some of your code as a minimal repro I'm happy to take a look.

FWIW, the verifyIdToken() API hasn't changed between our release versions, and our own testing hasn't revealed anything unusual.