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
Now that initializeApp supports no-argument initialization (release note, implemented in #8483), it would be great if initializeServerApp did the same. This would allow SSR web apps to use no-args init both on the server and the client.
Steps and code to reproduce issue
constserverApp=initializeServerApp();
The text was updated successfully, but these errors were encountered:
I'm trying your workaround and I'm getting a stack overflow error:
⨯ RangeError: Maximum call stack size exceeded
at String.replace (<anonymous>) {
digest: '2947813221'
}
I'm implementing the same cookie-based authentication strategy used in the friendlyeats-web Next.js sample. After a successful login, everything works fine, until I reload the page. On reload, the app crashes.
Previously, I was using initializeApp alone, and everything worked as expected... Any idea why?
Operating System
n/a
Environment (if applicable)
Node.js
Firebase SDK Version
n/a
Firebase SDK Product(s)
app (https://firebase.google.com/docs/reference/js/app.firebaseserverapp)
Project Tooling
Server-rendered web app
Detailed Problem Description
Now that
initializeApp
supports no-argument initialization (release note, implemented in #8483), it would be great ifinitializeServerApp
did the same. This would allow SSR web apps to use no-args init both on the server and the client.Steps and code to reproduce issue
The text was updated successfully, but these errors were encountered: