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
When cookies are disabled by the browser (which seems to be the case by default in private browsing for third party website, loaded on iframe for instance, then the getAuth throws an error. It's the same issue that has been reported here #5274 but the given answer isn't convenient.
I really think that in term of developer experience, it shouldn't be our role to check if the localStorage is available and depending on that, have a custom auth initialization, like I had to do here:
Hi @qlereboursBS, thanks for filing this. This is indeed a bug and the situation described should be handled gracefully (by falling back to in-memory storage). Do note, however, that the library will work in just a very limited capacity in this case---the session will not be persisted on refresh.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
When cookies are disabled by the browser (which seems to be the case by default in private browsing for third party website, loaded on iframe for instance, then the
getAuth
throws an error.It's the same issue that has been reported here #5274 but the given answer isn't convenient.
I really think that in term of developer experience, it shouldn't be our role to check if the localStorage is available and depending on that, have a custom auth initialization, like I had to do here:
If Firebase isn't handling this case, then the getAuth method is useless because we'll always have to check if the localStorage is available.
Steps to reproduce:
chrome://settings/cookies
then "Block all cookies"Thank you for your time, and sorry if what I suggest isn't possible
The text was updated successfully, but these errors were encountered: