Firebase DB Workaround for error: NullPointerException & component not present

Feedback
,
1

I found a workaround solution for all error users who are facing Runtime Error: NullPointerException (NPE) and for those who are getting popup errors like:

  • ‘Firebase Database component is not present’
  • ‘Cannot call ‘Get Value’ if the firebase object is NULL’

in companion while fetching data from Firebase Realtime Database (RTDB) and even for those who are addicted to old Firebase components.

The workaround solution

Guides
The workaround solution is to use an extension which is quietly sitting in a corner.
The extension (.aix) is Firebase Database Extended, created by @Ibrahim_Jamar .
You can download it from this link :backhand_index_pointing_right:com.firebaseextended.oi.firebasedatabaseextended.aix (20.0 KB) and if you wish to see a detailed guide :backhand_index_pointing_right: Free Firebase Database

Why this .aix?

As a long time user I would say this extension is one-of-a-kind replacement, to your long time used RTDB components. It has got almost all the properties of previous RTDB components.

You can use api key and URL address. *This is a temporary fix only.

The result?

I tested it on my testing project and got confirmed results as you were getting before the error started appearing. The companion and .apk responded to all blocks of my logic input without any issues or error…

To have it tested by yourself, I have attached my testing.aia project over here which will be deleted after a permanent RTDB components fix is released or within 2-3 days. Which ever is earlier.

Companion test video :backhand_index_pointing_down:

The blocks used in this test :backhand_index_pointing_down:

A visual programming interface displaying blocks for setting up Firebase database connections, reading and writing data paths, handling button clicks, and updating UI elements with database values. (Captioned by AI)
A visual programming interface displaying blocks for setting up Firebase database connections, reading and writing data paths, handling button clicks, and updating UI elements with database values. (Captioned by AI)735×1056 97.1 KB

The .aia

As you all developers know the value or importance of RTDB, I request not to misuse RTDB access and any of my personal data if you encounter during testing. Thankyou.
The .aia file :backhand_index_pointing_right: TestingVegaStar.aia (249.4 KB)

Conclusion

A humble request from my-side to all developers and users who are getting the above errors,
@Diego and Kodular staff are already aware of the current situation and they are trying their best to give you a permanent solution. They are not sitting quietly with their hand on hand.

Creating a new topics on the same issue is not helpful and it’s not even worth your valuable time. Try searching the topic first and check if the issue is already solved or under discussion. If there are none then its better to create a new topic.

For the above mentioned errors, there is an ongoing discussion in this topic :backhand_index_pointing_down:

Thanks for understanding
Happy K

1 Like
2

workaround needs to update the running live app. thats the main problem. otherwise for workaround web component is sufficient also.

1 Like
3

It does, did you check that… You can use this permanently.
It’s almost like a replacement of old database components.