Hi Thunkers, In my app, I had set up a listener on my loading page which referred to any changes in the Firebase RTDB Users root node. [image] I then added The data change block to each screen where I needed the Event Listener. [image] This was working at one stage but I haven’t visited it in a while. Today, I am in the process of tidying up my app and I hit a brick wall. The listener no longer works between screens. If you navigate away and then back again the listener stops triggering and only continues to work on one screen. I have tried to including a change Variable in just one listener block to one screen and add listeners to that variable on the other screens instead of the RTDB listener but that too does not work between screens. Does anyone have any ideas? I am completely stalled! :frowning:

Thank you for your reply @domhnallohanlon You suggestion regarding Variable names is noted with thanks. Here is a much simpler example that doesn’t involve Firebase: [image] Thunkable Screen two is a simple one second counter which works happily in the background. Screen one does not trigger the event listener for Variable ‘A’ that is changing every second in screen two. By pressing the button on screen one we can see that Variable “A” is indeed incrementing however Variable “B” is not being changed as the Listener is not being triggered. If I can solve this simple problem, I can fix everything in my more complex scenario in my other app. Thanks.

Hi @domhnallohanlon, Should I expect any support with this? Any work around I come up with is extremely inefficient and messy. Listener Callbacks are essential to my application. Am I doing something silly or is this a bug? Thanks.

hi. can you try the block? i see the value of a in the screen1 when click to button. [Untitled]

Hi @eddie.rebehy, I changed the variabes to [cloud] and your App worked like a charm. [image] I tested it without initializing the variables but did not work. Once the variables initialize [A] acted as expected.

hi @bilastois, If the listener is working, both labels will increment every second without clicking the button.

Hi @eddie.rebehy, As far as the code goes only [A] should incremented. Nothing is coded for [B] :grin:

Yes you are right. I just changed that. Thanks for making me aware that the listener works for initialised cloud variables. Unfortunately this won’t work in my case because the variable names are unknown. They are created when the user is created. Thunkable doesn’t have a block to allow initialization of a variable named variable. let me ponder on your discovery and see if I can find a way to make it work. Firebase is designed to work with thousands of listeners in one function. Unfortunatly Thunkable isn’t.

Have you tried the [Data Changed] event of Firebase. [image] It returns the [key] name and the [value] of this key. Using successive if statements you can determine which [key] was changed and what action you want to take. Just a suggestion.

This is what I started with. It won’t work on multiple acreens for me.

@muneer @domhnallohanlon [image] Thunkable And just like that…without any communication from the Thunkable beavers… It starts working for all variable types. Muneer; please confirm that I’m not losing my mind! Time to test this again in my app. :crazy_face: :roll_eyes: edit: you may have to clear your app cache to see this working.

I'm completely stalled with Event listeners

Questions about Thunkable X

eddie.rebehy November 1, 2020, 11:38pm 21

Worth posting this here. Thanks again to @drted .

Topic		Replies	Views
Multiple Listeners Questions about Thunkable X	2	2371	November 1, 2020
Issue with datachanged and Firebase Listener Questions about Thunkable X	10	872	May 12, 2021
Screen Start, Screen Open and Variable Change event sequence Questions about Thunkable X	1	835	December 14, 2020
Firebase data changed exploration Questions about Thunkable X	11	789	January 12, 2022
Detecting changes in Firebase - suggestions? Questions about Thunkable X firebase	4	398	July 14, 2021

I'm completely stalled with Event listeners

Related topics