Firebase Realtime Database component not working in Companion despite open Rules

Discuss
1

Hi everyone,

I’m struggling with the new Firebase Realtime Database component (the one that requires the google-services.json file). I’ve successfully migrated from the legacy component, but I’ve encountered a major issue during the development phase.

The Problem: The component works perfectly when I build and install the APK, but it fails to fetch or send any data when using the Kodular Companion. I receive a “Permission Denied” or it simply fails to trigger the DataChanged event.

What I’ve tried so far:

  1. Security Rules: I used a Python script to temporarily set my Firebase Rules to .read: true and .write: true. Even with the database wide open, the Companion still cannot access the data.
  2. Package Name: My google-services.json contains my specific Package Name (e.g., com.myname.myapp). I suspect the Companion (which uses io.kodular.companion) might be causing a mismatch.
  3. Authentication: I tried using the Firebase Auth component for a Google Sign-in, but as we know, Auth often fails in the Companion due to SHA-1 mismatches.

My Questions:

  1. Is it possible to use the new Firebase Realtime Database component within the Companion without compiling an APK every time?
  2. Is there a way to bypass the Package Name/SHA-1 check during development so I can test my logic in real-time?
  3. Do I need to add the Kodular Companion’s Package Name (io.kodular.companion) to my Firebase Project settings as a secondary app?

I have over 3,000 blocks in my project, so testing via APK only is extremely time-consuming. Any advice or workarounds would be greatly appreciated!

Thanks in advance.

2

See my response here:

As of now, building APK is the only reliable way. The priority yesterday was to fix the component so built apps stop throwing crashes. I’ll try to see if I can provide some hack for the Companion some time later toda…

3

Please! I’m in a terrible mess! The component gives me a Firebase Error
Permission Denied (after exporting to apk)
And this is even though technically it works and manages to get / store data normally.
And this happens mostly the first time every time the app is opened.
In addition to that, the event: initialize does not happen…
Please I need a solution!!!

4

If you can show the blocks or else check out these FAQs secttion