Firebase Console is not displaying live data

5,325 views
Skip to first unread message

Dominik Bleilevens

unread,
Jun 15, 2016, 11:13:30 AM6/15/16
to Firebase Google Group
Hello there!

I'm encountering an issue since two days.. my realtime database and its live data isn't reflected in the Firebase Console.
I have to reload the entire page, to see the current values, it does not fire the change neither the yellow update signals.
Nevertheless the data is actually updated, as I'm retrieving the values on a local website, where it gets updated as usual, but I don't see them on console.firebase.google.com

The code I'm using for communicating with my Firebase didn't change in the last days and it's really basic:

db.ref(path+'/points').transaction(function(points){
points += 1;
return points;
});

Did anyone of you also have this issue?

Regards,
Dom

Tim Stirrat

unread,
Jun 15, 2016, 4:31:45 PM6/15/16
to Firebase Google Group
Hi Dom,

Once you refresh the page do you get realtime updates for a while?

I'm wondering if this is related to the authenticated session expiring.

Do you see anything suspicious in the console log when there are no updates coming through?

Thanks,

Tim

Tim Stirrat

unread,
Jun 15, 2016, 4:32:41 PM6/15/16
to Firebase Google Group
One more thing, can you let us know the browser and platform (Windows/Mac etc)?

Thanks

Dominik Bleilevens

unread,
Jun 19, 2016, 11:04:16 AM6/19/16
to Firebase Google Group
SOLVED

I made some experiments and I think I figured out what the problem was.
I saved too many child nodes because I added every minute a child for more than 30 parents, so I think it was too much data to handle as I added more than 30 elements / minute and after a while this was too big.. at least this is my guess as it works now again after I cleaned up my data.

Regards,
Dom

Dominik Bleilevens

unread,
Jun 19, 2016, 11:05:18 AM6/19/16
to Firebase Google Group
Hey Tim!

No, from the beginning there are no realtime updates.
I was also used that the child trees are expanded when reloading if they were expanded before. Since the realtime database isn't updating in the console it always collapsed and you only see the top level project name.

In which console log?
If you're talking about my script updating the database.. this works perfectly and no error's are upcoming, as I think the data is actually updated. It's just not visible at https://console.firebase.google.com/

System info
Operating system: OS X 10.11.5
Chrome Version 51.0.2704.84 (64-bit)
Firefox Version 47.0
Safari: Version 9.1.1 (11601.6.17)

in none of those it's working. I think it also happened on another macbook when I worked on this project. 

Jacob Wenger

unread,
Jun 20, 2016, 2:42:50 PM6/20/16
to fireba...@googlegroups.com
This is "works as intended." When you have a lot of data in your database, we show a non-realtime view to make sure that your browser doesn't crash from all of the data we are loading. There should be a little indicator saying that you are in a non-realtime mode, but maybe we need to make it a bit more obvious. Thanks for the feedback.

Jacob

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/d758571d-9526-4c45-82e9-3a636ec81487%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Tim Stirrat

unread,
Jun 20, 2016, 2:55:49 PM6/20/16
to Firebase Google Group
Hey Dom,

There should be a warning when you are in non-realtime mode, but the warning seems to be broken. I'll fix it!

Cheers,

Tim

Dominik Bleilevens

unread,
Jun 29, 2016, 11:01:43 AM6/29/16
to Firebase Google Group
Haha it's not a bug it's a feature? ;-)
Warning is still "broken", at least I don't see any remark about it.

Tim Stirrat

unread,
Jun 29, 2016, 12:17:57 PM6/29/16
to Firebase Google Group
Hey Dom,

The fix is on its way, didn't make the latest cut, but should be in the console next week.

🔥

Tim
Reply all
Reply to author
Forward
0 new messages