Firestore connection bug

I need a fix or workaround asap. Our operations team has been blocked from making any changes for our customers the past 3 days.

@kporter @Tales_Rodrigues when you get a chance do you mind confirming your subdomains for me? Don't want to turn this on for the wrong customer(s).

I have tested this feature flag workaround and it works within my Cloud instance.

@ninjasitm @tavana_upkid let me know if you would like to try the feature flag workaround as well.

https://ardovia.retool.com/

Just enabled! You should see an option to set the Firebase database name. Set it to (default) , which should mimic what DEFAULT_FIREBASE_DATABASE_ID was trying to achieve and let me know if that fixes the behavior we are seeing!

1 Like

https://neighborride.retool.com/

The added config should look like this:

Just enabled it for you! Let me know how it goes

That worked for me, thank you!!

It worked. Thank you! Should I be prepared for taking any measures once the permanent fix is implemented?

Nope! Since this is an optional field you can just leave it blank going forward (or keep it as (default) up to you). If you really don't like seeing it in the UI we can coordinate rolling back the feature flag via DMs.

I'll update everyone here once the fix is live.

2 Likes

Please add us as well.
https://domos.retool.com/

Just added you as well!

@Wellington_Barbosa @nery let me know if you would like this feature flag to be turned on as well. If you do, please confirm your subdomain in this thread!

Please add us - https://upkid.retool.com/

Done! Let me know if you run into any other issues.

@BAbarquez I have the same issue, please add my team so we can have access to that new config. untappedathletes.retool.com

Done!

Please add us too https://arcadesoftware.retool.com/

Just added!

Please add us too https://justanothertest.retool.com/