Fix Firebase Auth Persistence on Production Domains#888
Conversation
Bypasses Safari ITP fallback on primary domains where Next.js proxies Firebase auth traffic, preventing users from being logged out on reload.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
1 participant
The app was aggressively falling back to
browserSessionPersistencefor all iOS and Safari users as a workaround for Safari's ITP (Intelligent Tracking Prevention) issues with IndexedDB auth persistence. However, Next.js proxying of/__/auth/traffic to Firebase makes auth traffic first-party in production, so ITP restrictions do not apply. This change ensures that we usebrowserLocalPersistenceon our primary production domains, preventing unexpected logouts for these users.PR created automatically by Jules for task 3218337396522034151 started by @DHCross