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
Logging with link auth working locally and deployed, but the __session cookie is not set when the application is deployed. When running locally the cookie gets set.
Sample network requests when running locally shows the __session cookie being set automatically after login
When running the same code on Firebase Hosting no __session cookie is set
[REQUIRED] Steps to reproduce
Deploy to Firebase Hosting.
Login with link.
Inspect network requets.
Refresh.
[REQUIRED] Expected behavior
The user should be set by SSR. The session should be available in the __session cookie.
[REQUIRED] Actual behavior
When deployed to firebase Hosting, the user is not set in SSR due to the __session cookie not being set. The user state is signed out on page load and the page updates after connecting to Firebase to show the user info.
The text was updated successfully, but these errors were encountered:
[REQUIRED] Environment info
firebase-tools: 13.5.1
Platform: macOS
[REQUIRED] Test case
Logging with link auth working locally and deployed, but the
__session
cookie is not set when the application is deployed. When running locally the cookie gets set.Sample network requests when running locally shows the __session cookie being set automatically after login
When running the same code on Firebase Hosting no __session cookie is set
[REQUIRED] Steps to reproduce
Deploy to Firebase Hosting.
Login with link.
Inspect network requets.
Refresh.
[REQUIRED] Expected behavior
The user should be set by SSR. The session should be available in the
__session
cookie.[REQUIRED] Actual behavior
When deployed to firebase Hosting, the user is not set in SSR due to the
__session
cookie not being set. The user state is signed out on page load and the page updates after connecting to Firebase to show the user info.The text was updated successfully, but these errors were encountered: