FG
๐Ÿ”Œ APIs & SDKsGoogle

Could not reach Cloud Firestore backend after upgrading to v9, but only in some projects

Freshover 3 years ago
Mar 14, 20260 views
Confidence Score85%
85%

Problem

[REQUIRED] Describe your environment Operating System version: Windows 10 Browser version: Chrome 97 Firebase SDK version: 9.6.5 * Firebase Product: Firestore [REQUIRED] Describe the problem After upgrading to Firebase v9 from v8, I'm encountering the following error in 2 of 4 environments: [code block] Here are the environments and results: GCP Project ID | GCP Firestore Region | After upgrading to v9 -- | -- | -- Firebase Emulator | None (local) | Works fine {project}-dev | us-central | Works fine {project}-prod | us-central | Could not reach Cloud Firestore backend {project}-prod-ca | northamerica-northeast1 | Could not reach Cloud Firestore backend The code in all 4 environments are identical and the CI/CD pipeline for the 3 GCP projects are identical. It's particularly noteworthy that `{project}-dev` works fine while `{project}-prod` and `{project}-prod-ca` don't. Steps to reproduce: To see the results, I created these 2 test pages. They both use SDK v9: {project}-dev: https://student-dev.examind.io/firestore {project}-prod-ca: https://student-ca.examind.io/firestore You will notice that `{project}-dev` loads firestore data just fine, while `{project}-prod-ca` doesn't and outputs this to the console after 10 seconds: There are a couple of related issues (https://github.com/firebase/firebase-js-sdk/issues/5667, https://github.com/firebase/firebase-js-sdk/issues/5932), but seeing different results in different projects with the same codebase may be a

Error Output

error in 2 of 4 environments:

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Moderate Confidence Fix
84% confidence100% success rate2 verificationsLast verified Mar 14, 2026

Solution: Could not reach Cloud Firestore backend after upgrading to v9, but only in some projects

Low Risk

@dconeybe Updated with source maps. The `firestore6` pages will be easiest to debug as they don't rely on a separate package in the monorepo. Looking for the `Firestore6/index.tsx` file in dev tools will allow you to put breakpoints in the code:

84

Trust Score

2 verifications

100% success
  1. 1

    @dconeybe Updated with source maps. The `firestore6` pages will be easiest to de

    @dconeybe Updated with source maps. The `firestore6` pages will be easiest to debug as they don't rely on a separate package in the monorepo.

  2. 2

    Looking for the `Firestore6/index.tsx` file in dev tools will allow you to put b

    Looking for the `Firestore6/index.tsx` file in dev tools will allow you to put breakpoints in the code:

Validation

Resolved in firebase/firebase-js-sdk GitHub issue #5977. Community reactions: 1 upvotes.

Verification Summary

Worked: 2
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

firebasegooglesdkapi:-firestoreneeds-infoneeds-attentionno-recent-activity