That sample project is sometimes working and sometimes not workings, can you figure its errors out please?
UberFirebaseExperiment__ne6.aia (16.8 KB)
This can't be good ...
Look up the Add Items to List block and tell us which comes first: the item, or the list?
So, to answer my question:
Let's compare that to the error message.
What type does the first block socket require, and what did the error message show for that first value?
i really dunno lol, so that i asked the help for fixing the error!
These don't help us diagnose crashes, do they?
Put some Notifier calls in those, and have them announce what the errors.
We can't fix what we don't see or hear.
Your description might indicate you need a way to run the findnearest button continuously. You said earlier the button some times works and other times it crashes.
You make a lot of calls to firebase and the MIT CloudDB server. Sometimes something is not connecting. One awkward way to continuously poll is to put that code in a Clock component to refresh the code (or part of the code, perhaps the large if statement) continuously.
Try a refresh rate at 5000 ms and see if that helps you app do what you want it to, if not change to 1000 ms or other values.
The crash is probably happening when you poll a database and you don't immediately get a response which may be some activities might have to be controlled by a Clock and an if statement to ensure you are grabbing valid data.
.
i guess the issue is not in the clock for how storing the locations, the issue is for getting the data back i think,i tired with adding the clock time to 5000 and 1000 and did not work
