最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

google cloud build - Firebase App Hosting backend configurations in apphosting.yaml are not applied - Stack Overflow

programmeradmin1浏览0评论

On March 12, 2025, there was an incident with Firebase App Hosting configuration:

The incident is supposed to be resolved but I am still getting errors with the apphosting.yaml configuration of my Next.js app. The only change is that now it happens at build time and not after it's been deployed.

Cloud Build Error:

unhandledRejection Error: Service account object must contain a string "project_id" property.
at <unknown> (.next/server/chunks/2256.js:107:1614) {
  type: 'FirebaseAppError',
  errorInfo: [Object],
  codePrefix: 'app'
}

I am using a Secret to store the private key value:

runConfig:
memoryMiB: 1024
cpu: 1

env:
  # Other env variables 
  - variable: SERVICE_ACCOUNT_PRIVATE_KEY
    secret: service-account-private-key

I tried changing the Secret and have the variable points to another version of the Secret, but no luck.

Any idea what can cause the problem? Is anyone in the same situation?

On March 12, 2025, there was an incident with Firebase App Hosting configuration: https://status.firebase.google/incidents/dMqtcJBwkmWeGDhmGqjN

The incident is supposed to be resolved but I am still getting errors with the apphosting.yaml configuration of my Next.js app. The only change is that now it happens at build time and not after it's been deployed.

Cloud Build Error:

unhandledRejection Error: Service account object must contain a string "project_id" property.
at <unknown> (.next/server/chunks/2256.js:107:1614) {
  type: 'FirebaseAppError',
  errorInfo: [Object],
  codePrefix: 'app'
}

I am using a Secret to store the private key value:

runConfig:
memoryMiB: 1024
cpu: 1

env:
  # Other env variables 
  - variable: SERVICE_ACCOUNT_PRIVATE_KEY
    secret: service-account-private-key

I tried changing the Secret and have the variable points to another version of the Secret, but no luck.

Any idea what can cause the problem? Is anyone in the same situation?

Share Improve this question asked Mar 13 at 11:47 lordofmaxlordofmax 8231 gold badge8 silver badges21 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

It's back to normal now for me, I rolled back to a previous commit with the Firebase App Hosting interface, it worked, and triggered a new rollout from my branch, it worked as well.

与本文相关的文章

发布评论

评论列表(0)

  1. 暂无评论