@Om_Bhat can you share an AIA for a real project to test? There was an entire rewrite of the component, and I want to make sure nothing breaks. Feel free to DM me if it’s private.
Using new libraries. Unfortunately I will have to deprecate the old FirebaseDB component, and create a new one. You will have to “rewire” the blocks where you use the old FirebaseDB to use the new one.
is firebase component is still in update progess? if yes how much time it will take? if already updated then just guide what can i do to update my projects. how to replace old component with new one.
Deprecate the old Firebase Database component (projects with it won’t build again)
Create a new Firebase Realtime Database component (won’t use the token authentication, only google-services.json). It will have all the blocks the same.
For app developers:
You will have to delete the old Firebase Database components (they will be highlighted in red in the component tree)
Add the new Firebase Realtime Database components, and add again the same blocks as they will get deleted in the previous step
Well that’s a quick solution though. I have no idea where it would go without your fast analysis.
Now it’s so quite, seems like a cyclone just passed by…
I’m still in cyclone, there are 20 customers with 500 to 2000 active users using apps. so first replace all components with all 20 different apps. and need to convenience to my customers to convenience their users to update the app.
atleast diego Replied and taking action to update thats why i got relief 1%. still 99% tension is walking with me.
The fix has been released. Please replace all your Firebase Database components with the new Firebase Realtime Database, and upload the google-services.json file.
@Om_Bhat or anyone else facing issues: does rebuilding the apps fix the problem?