(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.
test this.
diarypercobaan3_1.aia (10.7 KB)
first user will log in or sign up
it will proceed to the menu page.
from the menu page user may start to write and save. then will return to menu page.
from this point if user click read, it opens another page with list of tags saved under his user id in a listview. On clicking the listview it will show what was written in that tag on a label. like this i was modified slightly.
This logic will brings only the users data and not others data
Is like this do you want?
It can be still simplefied. But i believe using this logic you could try the remaining.
(Pls refer the user with name still in your fb structure)
hey soo i tried it out! and yes, that logic is what i want. ty for the help btw, i appreciate the effort sm. but when i tried connecting it to my phone, the listview still doesn't show up (?) the entries got put inside the fb structure but it's not visible when i tested it out
In the Baca screen, i set calling firebase tag as empty. Did you? Without making any changes try or try clearing your tinydb and try from the begining
avoid multi screens , also use virtual screens. Better ref multiple post and learn then complete your app.
I peeked at the various apps and the data, and saw
Your data base needs a good flush to get rid of old data not fitting your desired structure.
Also, your multiple screens have different ideas as to what the Firebase ProjectBucket is.
I jut straight up connecting it after downloading. Is there a step i missed or is that not what I'm supposed to do? 
--and I'm not sure what this means, I'm sorry English is not my first language.
since I'm using firebase for username, password, and entries, what should I set it to as then? Does leaving it " " in every screen works?
You have to understand how to get to each item in the Firebase data tree.
You start at the Project Bucket (blank is the root of the tree) and each part of the tag (parts separated by '/') sends you down a branch.
When you have traversed all the parts of the tag, what is left is the value that will return.
The sequence of branch choices that you make going from the root to your data is called a path.
This is very similar to finding a file deep in the Windows file system, folder by folder, from the drive letter c:.
So study how your tags and buckets work together to navinage through your data.
Lay out a map of how your data tree should look in the Database Console, using indentation.