I’m experiencing an issue when using multiple Firebase Realtime Database components in Kodular.
My Setup
I’m using three Firebase Realtime Database components connected to the same database but with different Project Paths:
- Firebase1:
rooms/39495/player/player1– Used only for listening to player1 changes - Firebase2:
rooms/39495/player/player2– Used only for listening to player2 changes - Firebase3:
rooms/39495/player– Used for GetValue and StoreValue operations.
Issue
When Firebase1 or Firebase2 is actively listening for changes through the DataChanged event, calling GetValue or StoreValue using Firebase3 causes the other components to stop receiving DataChanged events.
However, if I subsequently call GetValue using Firebase2, its DataChanged listener starts working again.
Expected Behavior
Each Firebase component should maintain its own DataChanged listener independently, regardless of GetValue or StoreValue operations performed by other Firebase components.
Actual Behavior
Using GetValue or StoreValue on one Firebase component appears to interfere with the active listeners of other Firebase components.
Question
Is this a known issue with the latest Kodular Firebase Realtime Database component? Is there a workaround to keep multiple Firebase components listening independently without having to call GetValue again to reactivate their listeners?