Firebase Database Crash - NullPointerException toLowerCase

A potential fix might be ready:

sample_1_1 (2).apk (6.5 MB)
samplevegastar (6).apk (6.5 MB)

@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.

seriously @Om_Bhat I couldn’t control your NPE. What was in that… :flushed_face:

And literally thank you @Diego for giving undo buttons on the designer and editor. Seriously thanks by heart… :handshake::handshake::handshake:

2 Likes

unable to share aia with you, can’t getting message button on clicking your profile

Send it to his email

yes how it is working? any workaround?

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.

It may take 1-2 hours…

Later i need to manually replace all firebase blocks?

That is correct, as well as migrate to use google-services.json (the token auth will be gone)

If i’m not wrong then I think every error user has to go through rewriting FBDB components and update their users.

Yes, so what I’ll do from my side is:

  1. Deprecate the old Firebase Database component (projects with it won’t build again)
  2. 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:

  1. You will have to delete the old Firebase Database components (they will be highlighted in red in the component tree)
  2. Add the new Firebase Realtime Database components, and add again the same blocks as they will get deleted in the previous step
  3. Build the app
  4. Release the app to your users

OK after your update just write here Component Update so i will refresh kodular and do replacing old component to new one.

1 Like

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… :tornado:

I’m also adding a visual red highlight to help identify which components are deprecated (as naming might be confusing):

New component tested and working. Note it doesn’t have token or DB URL as it uses google-services.json and it contains both:

I’m getting that merged and released soon. Will post an update once ready.

1 Like

I’m still in cyclone, there are 20 customers with 500 to 2000 active users using apps. :smiling_face_with_tear: 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.

1 Like

3 posts were split to a new topic: Runtime Error Cannot Invoke

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?


Published a detailed migration guide:

Error: Cannot find component.