nextjs-end rollout failed

[v0lsh3bnik]

I am using the nextjs-end repo for firebase app hosting, the build is working fine but i get an error on the rollout. I looked through the logs but nothing. Can someone help me please ?

[WCressman]

I currently have the same issue, I am following the tutorial step by step and App Hosting is failing

[ni7r0x]

In my case , I found out the issue by looking in Google Cloud > Logging > Logs explorer > SEVERITY > Error :

google.cloud.run.v2.Services.CreateService returns this error :

template.containers.resources.limits.cpu: Invalid value specified for cpu.
For the specified value, maxScale may not exceed 10.
...

Solved by adding the following lines to apphosting.yaml :

# Settings for Cloud Run
runConfig:
  minInstances: 0
  maxInstances: 10
  concurrency: 50
  cpu: 1
  memoryMiB: 512

I guess the Rollout Failure should be more verbose than that.

[AntonioGally]

I had the same issue with my nexjs deployments:
Google Cloud Build was successfully building my app, but in firebase console, my deployment launch was failing.
I've added this configuration in my apphosting.yaml that @ni7r0x commented (tks) and my deployment was completed

It would be great if the official docs mentioned this apphosting.yaml configuration file in the Basic Deployment section, and tell us if this file is required.

[gyula-szucs]

Had the same mildly frustrating issue.
Thank you @ni7r0x.

[r-dev-limited]

Mine just says all of a sudden: Ready condition status changed to False for Revision backlink-space-build-2024-10-28-003 with message: Deadline exceeded

[RebinX1]

i also have the same issue now, i have added the apphosting.yaml in my project but still i get the same error, one more thing is that at the start i was able to deploy 2 build to apphosting but after working on my app for a bit i started to get this error.

[ItsTeccs]

Currently experiencing the same issue with a valid apphosting.yaml file present in my project. Google console shows in the logs that the build was successful in the cloud, and my build locally is fine, but the rollout fails every time.

[vojdan]

I'm suddenly getting failed deploys with a successful build as well, just like in @RebinX1 screenshot.

Had to delete and redeploy the backend to get a working deploy.
Still seeing "Resource 'my-backend' already exists." errors in the GCP logs on re-deploy.

[Glimpse-Media]

I'm suddenly getting failed deploys with a successful build as well, just like in @RebinX1 screenshot.

Had to delete and redeploy the backend to get a working deploy.
Still seeing "Resource 'my-backend' already exists." errors in the GCP logs on re-deploy.

I am currently dealing with this same issue and have been for 2 days, have you possibly found a resolution?

[josephkabba]

Having the same issue, it looks like next build is not being run, and the official docs don't explain how to get the environment to build next-js apps for some reason, It thinks it's an angular application, which is not the case. Please, the Firebase team, make this very clear in the documentation.

[ItsBenDov]

I have the same problem too. it looks like the build was completed, and the revisions in Cloud Run show that the build was successful, but firebase still shows that the build have failed in the console.

[Msekoo]

same problem, and i fixed apphosting.yaml config problem, the revisions in Cloud Run show that the build was successful, no any error. but firebase still shows that the build have failed in the console.

[ItsBenDov]

Looks like that's happening for a lot of users
see this reddit thread:
https://www.reddit.com/r/Firebase/comments/1k1f321/error_occurred_in_app_hosting_rollout/

report it to the firebase team for them to fix it.

[jimmy-chiang]

Same here. The build was successful but the rollout failed. And the logs explorer says:
"The request was invalid: build "build-2025-04-18-002" was not found and is invalid"