Firebase Database Crash - NullPointerException toLowerCase

Como guardas el valor en una variable? coloco el link y la ruta en el navegador y obtengo la respuesta de firebase, pero como hago para guardar valores y obtener vlores en una variable?

Yo actulice Kodular, cambie los componetes viejos por los nuevos. me sale el error. instalo el apk en mi celular y no funciona. no tengo acseso a Firebase

Using multiple “instances” of the new component will crash?

No, they will work fine.

Las aplicaciones que tengo instaladas en PlayStore que estan compiladas con la version anterior de Kodular ya funcionan bien, ya funciona Fire base.

las aplicaciones con la nueva actualizacion de Kodular no funcionan. error en Firebase

Firebase has normalized things here… you can revert to the previous settings.

Respected diego Sir, As so many people are rely on kodular with their small running business as like me, if its possible to revert setting to previous you have to do this earlier as topic created. As personal, there are my 20+ clients with almost 25k+ active users using kodular applications. Before releasing any update check it carefully, and this release affection should towards new apk build release only, not for old exported apps. We are not here to listen Mamma’s like reason. You better know How it suffers when need to listen thousands of mouth if update failed. Thank You.

2 Likes

I have build the APK in same way, but authentication is failing with Google/ EmailPass. Also not geting value from realtime DB

Revisar en Kodular:
Nombre de la Aplicación
Package Name
CodigoDeVersion
Api Keys “Todas borradas”

Check in Kodular:
Application Name
Package Name
Version Code
API Keys “All deleted”

Por eso me sale el error con Firebase

That’s why I’m getting the error with Firebase.

The situation has somewhat normalized and is working now. My main applications seem to be resolved, but I have a question. We were able to use multiple databases in one application, for example, two databases in a Firebase project. I edited the Google Services JSON file and added the URL of the database we were using, and the problem was solved. But what about databases in different Firebase projects, for example?

So, I want to pull data from application A into application B. For this, I need two applications and, naturally, two different Firebase projects.But Kodular gets all the new component information, URLs, etc., from Google Service JSON. What should we do in this situation, @Diego ?

2 Likes

i also need to pull URL from 2 diferrent Projects, please let me know if you can do this currently

1 Like
Original content

Olá a todos, Recentemente migrei meu projeto do componente legado para o novo Firebase Realtime Database, seguindo o guia oficial. Porém, estou enfrentando um erro persistente ao tentar salvar ou ler dados.

Fluxo do meu app:

  1. Na Tela 1, o usuário faz login via Firebase Authentication. No LoginSuccess, eu salvo o user ID gerado no TinyDB.
  2. Na Tela 2, antes de qualquer operação no banco, eu ajusto o Project Path do novo componente usando um join: "profissionais/" + TinyDB.GetValue(user ID).
  3. Depois, eu chamo o StoreValue (ou GetValue para checar dados).

Notas importantes (O que já testei):

  • Eu NÃO estou usando o Companion. Estou compilando o APK e testando direto num celular real.
  • O arquivo google-services.json está nos assets.
  • O Nome do Pacote no Kodular está idêntico ao do console do Firebase.
  • Eu garanti que o bloco de ajustar o Project Path está antes de qualquer chamada de ler/gravar.

O Erro: Quando os blocos rodam no APK, eu recebo este erro: [firebase database component is not present]

Existe algum bug conhecido no novo componente perdendo o contexto entre telas, mesmo usando o TinyDB para passar o UID? Ou tem algum passo extra necessário? Anexei meus blocos abaixo. Agradeço qualquer ajuda!

Hello everyone,

I recently migrated my project from the legacy component to the new Firebase Realtime Database, following the official guide. However, I’m encountering a persistent error when trying to save or read data.

App flow:

  • On Screen 1, the user logs in via Firebase Authentication. In LoginSuccess, I save the generated user ID in TinyDB.
  • On Screen 2, before any database operation, I set the Project Path of the new component using a join: "profissionais/" + TinyDB.GetValue(user ID).
  • Then I call StoreValue (or GetValue to check data).

Important notes (what I’ve already tested):

  • I am NOT using the Companion. I’m compiling the APK and testing directly on a real device.
  • The google-services.json file is in the assets.
  • The Package Name in Kodular matches exactly the one in the Firebase console.
  • I made sure the block that sets the Project Path runs before any read/write call.

The error: When the blocks run in the APK, I get this error:
[firebase database component is not present]

Is there any known bug with the new component losing context between screens, even when using TinyDB to pass the UID? Or is there an extra step required? I’ve attached my blocks below. Thanks in advance for any help!

Translated by RaYzZz

I’m also receiving the message “Firebase Database component is not present”.

I followed all the procedures.

I replaced the Firebase component with RealTime, deleted the old component, and imported google.json. But the component doesn’t initialize.

1 Like

Yo tenia el ,ismo problema.
en mi caso la solución fue: Eliminar componente ONE SIGNAL NOTIFICATIONS ó extension de ONE SIGNAL NOTIFICATION

Yo lo elimine y ahora Firebase si se conecta sin errores con mi aplicación

1 Like

Yes, in my case the native Firebase Cloud Message component is conflicting with RealDataBase. I removed the FCM component and it worked. But we need to resolve this because it no longer works with the old FCM extension I was using either.

I was looking at the Migration Guide in the docs, and honestly, it feels like a lot of heavy lifting for the average user.
Instead of asking everyone to go through these complex manual steps or roll back versions, wouldn’t it be much better if the Firebase Component was updated to handle modern libraries natively? It would save everyone a lot of time and keep the no-code experience smooth as it should be​:folded_hands:t3:

@Diego Do you have a fix to let the FB database run with companion? or do you feel it cannot be fixed anytime soon? We really need to have atleaset firebase database or other component working with companion as its the only simple way for testing out apps fast. instead of downloadin the apk everytime and installing it.

Hi, sorry for the radio silence these past days, I’ve been quite busy with other topics. No, not yet, I don’t have a fix for the Companion. I’ll resume working on it this next week.

1 Like

Boa noite ! Eu migrei conforme o manual de migração , mas ainda está aparecendo a mensagem [componente fire base os not present] será que o senhor poderia me ajudar?

I’m having trouble using any messaging components like FCM and Onsignal because there’s an incompatibility issue with RTDB, which is likely causing problems for other users. Is there a way to resolve this?