getValidIdToken and getValidCustomToken return old server token on subsequent calls

[mfellner]

getValidIdToken and and getValidCustomToken only return the fresh token once, immediately after refreshing. Otherwise the functions return the argument serverIdToken or serverCustomToken which is likely the original, expired token. This is because internally the expiry check happens against the cached, fresh token.

Should be fixed by #290

[SebaRiccardo]

I am having the same issue, and it took me a while to realize that the library was the problem, not my code. It was driving me crazy.

[awinogrodzki]

Hey @mfellner @SebaRiccardo!

I have merged the PR into canary branch. Thanks so much for help with this @mfellner!

The fix should be available in next-firebase-auth-edge@1.9.0-canary.2.

Let me know how it works :-)