Firestore connection bug

💬 Queries and Resources
1
  1. My goal:
    Query my Firestore
  2. Issue:
    Existing code that used to work now shows an error.
    Whenver I try to run Query in Raw mode, using an Firebase resource, I see the following error:
  • message:"ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined"
  1. Steps I've taken to troubleshoot:
    Query in GUI mode does work, creating a new Firebase resource with a new key didn't help, same error for existing app, and for a new app.
  2. Additional info: (Cloud or Self-hosted, Screenshots)
    Screenshot 2025-06-06 at 18.20.55
    Screenshot 2025-06-06 at 18.20.551804×1122 173 KB
1 Like
2

I'm facing the exact same problem. It was not happening until today. Now, any query i try to do give me the error:

message:"ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined"

I hope we find a way to fix this.

1 Like
3

Same problem here with raw mode queries on Firestore

error: "ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined"

4

Seems that it works fine now.

5

This still seems to be an issue when using Firestore query in raw mode. The connection passes the test but running the query suddenly results in "ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined"

2 Likes
6

Same problem here. All raw Firestore queries stopped working. And this seriously compromises our app and users. We need a quick solution.

2 Likes
7

Hey everyone! Do you mind sharing the resource configuration for these queries? We recently added the ability to select non-default database IDs and want to see if this behavior is connected to that release.

8

Hi! Thanks for your reply. Here's an example. Let me know if you need anything specific.

Screenshot 2025-06-09 at 14.43.24
Screenshot 2025-06-09 at 14.43.24493×794 44.5 KB

Screenshot 2025-06-09 at 14.43.45
Screenshot 2025-06-09 at 14.43.45972×794 54.8 KB

9

Having the same issue, this is making a large portion of our app not useable, also need a fix asap!!

10

The resource query is setup by copying the service account key.

11

How can we specify the database ID? Need a quick workaround for this.

1 Like
12

I have the same configuration

13

Thanks for that context everyone! Looks like there is an issue with Firestore queries in raw mode using the default database name. I've notified our engineering team of this behavior and they are looking into a potential fix now.

In the meantime there is a feature flag that I could flip on that would potentially allow you to workaround this issue by declaring the database ID manually. Let me know if you would like to explore that route while we wait for the more permanent fix!

14

How long is the permanent fix going to take?

15

Any chance this feature flag could make things worse? And would we need to make a change on each query? It doesn't seem too viable. I'd rather wait for the permanent fix unless you think that can not be done today still.

16

Don't have an exact timeline but we have already identified a potential fix and are testing it locally right now.

Totally understand if you are wary of fiddling with things. The feature flag would just allow you to specify the database name in the resource settings, you would then set it to '(default)' to mimic the DEFAULT_FIREBASE_DATABASE_ID variable that is not being parsed correctly.

17

I am open to the feature flag. My app is down without firestore working properly. What do I need to do?

18

Same issue here.

19

Sounds good. Please flip on the feature flag.

20

I'm curious though. If you don't mind, why wasn't it possible to simply revert the change that caused the issue in the first place, at least as the temporary fix?

And, more importantly, if the the feature flag doesn't work will it be as smooth flipping it off?