You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it's supposed to be cached locally but calling FirebaseUser.GetIdToken(false) is still very slow even for 2nd or 3rd calls (and the returned token is the same). It takes seconds for the result for some reason. I thought our API server was slow but while debugging another issue, I found out this method is what holding it back. When I introduced our own local token cache, the speed significantly improved.
Is there some special logic with this method call that makes it so slow? Also is it safe to cache the token for 50 minutes (I assume it expires in 1 hour)?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I know it's supposed to be cached locally but calling
FirebaseUser.GetIdToken(false)
is still very slow even for 2nd or 3rd calls (and the returned token is the same). It takes seconds for the result for some reason. I thought our API server was slow but while debugging another issue, I found out this method is what holding it back. When I introduced our own local token cache, the speed significantly improved.Is there some special logic with this method call that makes it so slow? Also is it safe to cache the token for 50 minutes (I assume it expires in 1 hour)?
Beta Was this translation helpful? Give feedback.
All reactions