Sorry to hear you’re now running into a 404 error here, @Fsl.
I did some checking and it looks like we’ll sometimes see a 404 when the account connection to Firebase/Firestore was added with the Project ID and it needs to use the RTDB (Realtime Database) Project ID instead.
Can you reconnect your app account and use the projectId in the following format: projectId-default-rtdb. For example, if your projectId was project123 you’d use: project123-default-rtdb
After it’s reconnected with the RTDB Project ID, could you try pulling in a new test record and confirm whether that works?
Hi, I have used this new format and the connection is failing.
“Unable to verify that your connection has access to the Firebase/Firestore project "edexia-default-rtdb””
Page 1 / 2
You are most welcome @nutrion!
If there’s anything else we can help with in the meantime please do let us know!
Thank you @SamB, hoping this gets resolved soon.
Thanks for sharing those screenshots here, @nutrion
I reached out to the team about this and they’ve re-opened the bug report. You’ve been added to it so you’ll get a notification as soon as it’s been fixed.
In the meantime, the account connection would still need to be manually reconnected. Very sorry about that. Really appreciate everyone’s patience on this, I do hope it can be resolved soon!
Hi @JammerS, once I reauthenticate everything runs smoothly. Then, after some hours (perhaps 24?) I get an email saying there are issues with my Zap, and to reauthenticate.
Here’s the requested screenshot of my Zap history:
The error code is 400: invalid grant.
Here’s an older screenshot showing that Zap did successfully run at some point, then started erroring again.
Thank you for your support on this issue.
Hi @nutrion,
Are you encountering any error messages when executing your Zap? Please post a screenshot of your Zap history along with the error message so we can determine which direction to direct you to resolve your issue. We’ll be looking forward for your response. Thanks.
Hi @JammerS, I am still running into this issue and there is no option to update the app, even when following exactly the steps outlined in the post. I just filed a support message, really appreciate help on this
It looks like the bug report has been closed. If you’re still running into this issue. I’d recommend reaching out to our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.
Hi, i’m still experiencing the same trouble.
as my issue seems to be solved, dropping a note from Zapier support to anyone lurking. Make sure you’re using the latest version of the integration.
Hello, how did you solve the FireBase problem?
Thanks for letting us know @Mary Bookings! I’m so glad you were able to get things resolved by upgrading your Zaps to use the latest version of the Firebase / Firestore app!
It looks like the bug report has been closed. If you’re still running into this issue. I’d recommend reaching out to our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.
Hi, i’m still experiencing the same trouble.
as my issue seems to be solved, dropping a note from Zapier support to anyone lurking. Make sure you’re using the latest version of the integration.
Hi there @GTHuser,
It looks like the bug report has been closed. If you’re still running into this issue. I’d recommend reaching out to our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.
Hi, i’m still experiencing the same trouble.
Hi there @GTHuser,
It looks like the bug report has been closed. If you’re still running into this issue. I’d recommend reaching out to our Support Team here: https://zapier.com/app/get-help
I appreciate your patience and understanding.
I am also having the same issue. Can you please log me too?
Hi @Kaleb,
Thanks for bringing this to our attention.
I have added you as contact information to the open bug report as another affected member. We will let you know via email once the bug has been fixed.
I appreciate your patience and understanding.
I’m also experienceing this issue. Firebase auth requires constant maunual reconnection.
Hi @amtrekker,
I have added you as another affected member to the open bug report. While we can’t provide an exact ETA for the bug’s fix. We will let you know via email once it is.
I appreciate your patience and understanding.
@SamB I’m also experiencing this same issue, would you mind adding me to the list, please?
Hi @MinhTV and @BeauIVI, thanks for reaching out here.
@MinhTV - I’ve added you to the bug report too so we’ll definitely notify you once’s it’s been sorted.
@BeauIVI - really sorry for all the hassle caused by having to manually carry out the work that should be being handled by a Zap.
Adding new folks to the bug report does help to bump up it’s priority but unfortunately I can’t give any kind of estimate as to when a fix can be expected. There aren’t any workarounds reported that could get around the frequent reconnections needed, but if I come across anything on that front I’ll be sure to share details of that here.
Thank you all for your ongoing patience on this, I do hope a fix will be implemented soon!
I’ve had a few emails with support on this issue. Its been present on my end since Nov 2023 and still ongoing.
Would love a workaround as its causing so much manual work not having my set zaps run for such a simple task.
Anyone having a better experience on a different platform?
Hey, i got the same problem, can you add me on the list to notify, when firebase is working correctly again
Thank you for the update.
I tried to implement a work around by setting up a zap that would create a dummy document once every hour in the hopes that it would keep the session alive. Unfortunately, it does not.
It seems as if something is killing the refresh token on the Zapier side. But there is already a bug reported so hopefully that address it.
David
Thanks for reaching out here @David Hardenbrook. I’m so sorry you’re running into that bug as well.
I’ve just checked back in on the bug report and it appears to still be ongoing. I can’t make any promises around as to when it would be resolved by. But I’ve added you to the list which will help to increase it’s priority, and ensures that you’ll get an email notification from us the moment it’s been resolved.
Thanks for your patience in the meantime. As soon as I get any updates on this I’ll be sure to pop back in the thread here to keep you all in the loop!
I’m experiencing this same issue. Are there any new updates?
Thank you.
That’s great news @99plus! I’m so pleased to hear that migrating the database over to US hosting helped to resolve the issue.
Except the authentication expires every couple of days, leading to the automation failing. How can I make the authentication permanent?
Ah yes, it looks like the Firebase / Firestore app doesn’t automatically renew it’s authentication tokens like some other apps do. So if the Zap runs and tries to use an expired authentication token then the step will fail.
I did some looking into this and it seems there’s a bug reported where the authentication tokens are expiring too frequently and not being automatically renewed. So I’ve gone ahead ahead and added you to the list of folks being impacted by this issue which will help to increase it’s priority. I can’t give any sort of ETA as to when this would be fixed by but we’ll be sure to notify you by email as soon as it is!
There aren’t currently any workarounds reported for automatically reconnecting your Firebase / Firestore app account unfortunately. You’d need to continue reconnecting your Firebase / Firestore app account manually. Sorry for the less than ideal news here, but if we come across a workaround for this in the meantime we’ll share details of it here!
Hi, I’ve migrated to a US-hosted database and everything is working.
Except the authentication expires every couple of days, leading to the automation failing. How can I make the authentication permanent?