It only does not work when I wait for +60 Min. Even though I refresh the token, firebase seems to not work
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
1 Like
And with a clock do you know if it works?
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
1 Like
I used the same solution for now. Thanks. I will try (uffff waiting an hour for each solution tried…)
1 Like
Now you using firebase auth I’d token in real-time database.
But your need to use web keys in real-time database.
And firebase real-time database is not secure
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 
It not possible. I think
I think the problem is the first token. Im trying to get 2 different id tokens with a clock. Ill tell results in 1 hour
Are you try to see data only in your admin panel app
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.