eeeyupp still doesn't work
(even when i used the old blocks)
I can only give you general advice here.
Know your bucket.
Know the path in your tag.
Verify those against what you see in the Firebase data console.
they all have the same bucket, and im not sure by what u meant with verify against what i see in Firebase data console. the tag have a join block, but for some reason it couldn't retrieve that... but when it's without a join block (like the new blocks but then new problem got there--) it could be retrieved. is the join block the problem? or am i missing something here?
where dewi is the user signed into the app, this will return a dictionary (json string) of all their diary entries.
does that mean it can't do it automatically and need to be manually written?
like for ex there's another user, does that mean when they logged in I have to renew the tag every time?
No, set the signed in user to a variable, and use a join block to build the path
if i initialize global user to " " would it still work? so if a new user came in i dont have to change the initialize user to. and i have this trouble when i use join block i cant get the value for some reason (??)
You can set the user when they register/login.
sorry english isn't my first language so im still confused. i have to change it manually w every new user?
Will the user login to the app, with their username ? If so, you can capture it at that point and set it to your user variable.
Otherwise the user may need to provide their username so that they can return their diary entries.
yeah, they will use their username. for some reason it still doesn't work, I don't understand what's wrong...
(Canned Reply: ABG- Export & Upload .aia)
Export your .aia file and upload it here.
.
I'll send it in around 8 hours or so!
here's the old one w the old block (where the issue is i can't retrieve the user's diary entry from firebase AT ALL):
diarypercobaan3 (1).aia (11.4 KB)
and this one is the newer block (where i can retrieve what the user's previous entries are, BUT the issue is other user's entries can also be seen even though I logged in with a different account)
PERBAIKANdiary.aia (10.5 KB)
thank you for your time by the way!
In your second aia, you have not done what I suggested:
You are storing the currentUser to tinydb, so why do you not use it to return that user's diary entries
oh right, my bad. for returning the user's diary, it's tinydb get value right? the block can't be put on under the call firebase so i use if block.
PERBAIKANdiaryLAGI.aia (11.4 KB)
and it still doesn't work
ps: it does return the firebase but it's still all the other account's data too. also for the 2nd block (the Perbaikan one) the format in Firebase is rlly messy. the first block's Firebase format is cleaner, but I just can't return the data from them
Old Firebase Format of the first block (percobaan3)
New Firebase Format of the second blocks (Perbaikan)
Suggest go back to the original firebase structure, which keeps individual users diary entries separate from other users. This is how it would work if you were using Firebase Authentication for your users.
but if i use that, i still can't return stuff from the firebase... idk how to do that...
okay so this is the original one. but i still can't retrieve anything at all. i tried ur way previously, still didn't work though... and then i tried doing it with tags different way, add tinydb too to call the currentuser. still no result. i don't understand anymore 
diarypercobaan3 (3).aia (11.5 KB)
I will take a look a bit later on.