@ganjar added!
Please enable for this: https://latimer.retool.com/
@eltoncandido_sampaio added you as well
I get: Saving failed.
You already have a resource named "Firebase" when I try to add default
DM'd you @eltoncandido_sampaio!
I replied to this thread earlier today but I'm still not seeing the feature flag
This is for getscope.retool.com
Just added you @SamiBaguneid , let me know if you still don't see this field
Thank you its working now
1 Like
@BAbarquez please this as well: https://mudancaseconomicas.retool.com
Hi! Can you please add us as well: https://layerapp.retool.com
I agree with the others saying that such a bug should not occur. It is affecting our production workloads, for example.
But even worse so, what kind of response is this?
Obviously, this bug is affecting many users. And the best you can do is let us write down our Retool organisations here, in the open internet, so you manually enable that feature flag?
Why not activate it for everyone or roll this broken feature back?
1 Like
@eliasjnior @Jean-Baptiste_Castro @Zach_Soflin just enabled it!
@j9120 the original scope of impact looked to be smaller than the number of customers reaching out on this thread, we are currently exploring turning this flag on for all Cloud orgs.
In the meantime, do you want us to enable this flag for your organization? If you are not comfortable sharing your subdomain on this thread please DM it to me.
Hey everyone! While we wait for the fix to land in prod, we have enabled the feature flag that exposes Firebase database name for all organizations. If you are encountering the ReferenceError: DEFAULT_FIREBASE_DATABASE_ID is not defined message, please set this field to (default) in your resource config like so:
Hi, please can you add: https://developerhut.retool.com/
Hey @Taylor_Gibb , this should have been rolled out to your organization when we flipped the feature flag on for everyone here.
Let me know if you don't see the Firebase database name field in your resource configuration!
Thank you, I do appreciate the quick response and action! It works again now.
Hi, please can you add: https://driftlearn.retool.com/
Hey everyone, thanks again for your patience while we worked on this issue!
Just wanted to let you all know that the fix has ben deployed to prod and you should no longer be running into this error message (just tested this out myself and clearing the Firebase database name field works as expected).
3 Likes