[NEXT]: new framework with app router is unaccessible after deployment to firebase/cloud-functions

[RichardIvan]

[REQUIRED] Environment info

global firebase v - 11.30.0

Repository is using pnpm. The next app is within a workspace.

project firebase
"firebase": "^9.22.0",
"firebase-tools": "^12.1.0"

firebase config

{
  "hosting": {
    "source": "./",
    "ignore": [
      "firebase.json",
      "**/.*",
      "**/node_modules/**"
    ],
    "frameworksBackend": {
      "region": "europe-west1",
      "cpu": 1,
      "maxInstances": 1,
      "invoker": "public",
      "cors": true,
      "ingressSettings": "ALLOW_ALL"
    }
  }
}

firebase-tools:

Platform:
macOS

[REQUIRED] Test case

N/A

[REQUIRED] Steps to reproduce

firebase deploy of the frameworks enabled nextjs app

[REQUIRED] Expected behavior

example.com/api/endpoint does not throw 500, Invariant: failed to start render worker Error: listen EADDRNOTAVAIL: address not available

[REQUIRED] Actual behavior

Local, emulator works as expected including nextjs /app/api/* function
Deployment is successful and the Nextjs framework app.

When deployed, GET request function works as expected.
When trying to access POST request, we see a failure even if the functions are the same - basically trying to return 200 status with empty object.

Requesting POST API endpoint fails with 500. "Invariant: failed to start render worker Error: listen EADDRNOTAVAIL: address not available"
Logs in GCP don't provide much of additional information.

[justinh00k]

I am also getting this error on the cloud function of my NextJs firebase hosting app.
Invariant: failed to start render worker Error: listen EADDRNOTAVAIL: address not available 199.36.158.100

[rchaz]

I'm hitting the same error

[rchaz]

Error on the SSR function deployment post upgrade to nextjs13 app router -

Invariant: failed to start render worker Error: listen EADDRNOTAVAIL: address not available 199.36.158.100
at Server.setupListenHandle [as _listen2] (node:net:1723:21)
at listenInCluster (node:net:1788:12)
at GetAddrInfoReqWrap.doListen [as callback] (node:net:1937:7)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:8) {
code: 'EADDRNOTAVAIL',
errno: -99,
syscall: 'listen',
address: '199.36.158.100'
}
Container called exit(1).
Error: Process exited with code 1 at process. (/layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src/invoker.js:92:22)

[slecoustre]

The crash of the function appeared with the next version 13.4.3 only on firebase in local it works very well

but the problem for POST, PUT ... APIs with a Body appeared since next 13.3. it works if you don't use the emulator but if you use the emulator or deployer it doesn't work 500

[justinh00k]

Looks like same as vercel/next.js#49777. I was able to workaround by reverting to next 13.3.4, which also meant I had to add experimental.appDir : true to next.config.mjs and __NEXT_PRIVATE_PREBUNDLED_REACT="next" (with two underscores) to my .env.

[slecoustre-vulog]

With version 13.4.2, the site works well on firebase but the problem on Route Handlers persists for methods other than GET

[ameddin73]

This is a major blocker, any progress on this?

[slecoustre-vulog]

The bug is still present in the latest version 13.4.4 😔

[michaelangeloio]

Any updates?

[michaelangeloio]

The above PR resolved the issue for me @slecoustre @ameddin73 @rchaz @justinh00k

[slecoustre-vulog]

@michaelangrivera
Thanks.

Some developers have the same problem on AWS.

I think the problem is with Nextjs.