Maybe this will help you, currently it works in my app without any problem, for me it’s a direct way to work with firebase without the need of extensions, just the web component.
Yes please. but am I not doing what your saying? I mean each time the user gets in the Screen 1 (opens the app) Im calling a new token. I checked it because I got into 2 or 3 times and I noticed it changed.
If you are in the same screen for an hour and you want to reset a new idtoker you can do it with a clock to get a new idtoker automaticaly.
You will have the same id token… each hour the idtokens change
i remember there was a bug that you get permission denied when you auth with the screen.initialize… i dont know if it is fixed… if you set the same with a botton the bug is fixed
Because this project was a test, but in my real app my login does not exist (because auth is via sms phone), so once the user is registered he will automatically jumps from screen 1 to his home
ones a make a proyect to reset idtokens after it expires with a clock. the easiest solution i used was set the rule “write: true” but i dont know this is a problem to your proyect. you can try with a clock to log in after some seconds later the screen initiaze and share us the results
I know it will work if I set the rules true and place that API Key as Firebase Token, but actually is exactly that’s what I want to avoid. I do not want my DB to be .read and .write public