Gen2 Firestore Triggers fail with LOCATION_POLICY_VIOLATED on Named Firestore Database in me-central2

Google Cloud Serverless Applications
,
1

Hi everyone,

I’m facing an issue deploying Firebase Cloud Functions (Gen2) with Firestore triggers.

Project details:

  • Project ID: (PII Removed by Staff)
  • Firestore database: (PII Removed by Staff)
  • Firestore type: Native
  • Database region: me-central2
  • Cloud Functions Gen2
  • Firebase Blaze Plan

The Firestore database migration completed successfully.
Rules and indexes deployed successfully.
Callable and scheduled functions deploy successfully.

However, every Firestore document trigger fails to deploy with:

LOCATION_POLICY_VIOLATED
Permission denied on locations/me-central2

Examples:

onDocumentCreated
onDocumentUpdated

I verified the following:

:check_mark: Eventarc provider exists in me-central2

gcloud eventarc providers describe firestore.googleapis.com --location=me-central2 --project=shebara-ride

The provider lists all Firestore document event types:

  • google.cloud.firestore.document.v1.created
  • updated
  • deleted
  • written

:check_mark: Firestore database exists and is healthy

gcloud firestore databases describe --database=(PII Removed by Staff) --project=(PII Removed by Staff)
Output:

  • Location: me-central2
  • Type: FIRESTORE_NATIVE

:check_mark: IAM

  • Project Owner

:check_mark: Organization Policy
No resource location restrictions.

If I deploy callable or scheduled functions, they deploy successfully.

Only Firestore document triggers fail.

Questions:

  1. Is there any known limitation for Gen2 Firestore triggers on named Firestore databases in me-central2?

  2. Why does Eventarc report LOCATION_POLICY_VIOLATED even though the Firestore provider and Firestore document event types are available in me-central2?

  3. Is this a backend issue or is there an additional configuration required?

Any guidance would be greatly appreciated.

Thank you.