The useFrappeAuth() hook's currentUser remains undefined even after successful login

[ahmad-91]

Core Problem
The useFrappeAuth() hook's currentUser remains undefined even after successful login, causing the SDK to fail in maintaining authentication state.
Specific Issues
Session State Not Updating
frappeLogin() succeeds but currentUser never gets set
SDK state doesn't reflect successful authentication
Session restoration doesn't work on page refresh
Cookie Management
No session cookies are being set after login

[nikkothari22]

Is your frontend React app hosted on a different URL than your backend? If yes, that's the reason why the cookies are not being set. It's not a limitation of the library, that's just how cookies work.

For cross domain requests, use OAuth bearer tokens instead.

[Kail3913]

Hi, I had the same issue, and thanks for the answer, but what if I want to use cookies based authentication and I'm just using a different URL while I'm in local development?

Run bench build after every change is not a good experience, what would be your advice in that case?

[mrobles-paystand]

I was using frappe manager for the backend and I just added a custom file to the site nginx proxy with the config to send the traffic from my site url dev.localhost/gat-local/ to localhost:8080/gat-local/ which is running in my devcontainer.

If this helps someone I'll leave the custom file here, you should create it in the path (remember to use your site and app name) sites/dev.localhost/configs/nginx/conf/custom/gat-dev.conf

# Development configuration for GAT Admin
# Proxy /gat-local/ to the development server of Vite (port 8080)
location ^~ /gat-local/ {
    proxy_pass http://fm__dev_localhost__frappe:8080/gat-local/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    
    # For WebSockets (Vite HMR)
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    
    # Timeouts for development
    proxy_connect_timeout 60s;
    proxy_send_timeout 60s;
    proxy_read_timeout 60s;
    
    # Buffer settings for development
    proxy_buffering off;
    proxy_request_buffering off;
}

Hi, I had the same issue, and thanks for the answer, but what if I want to use cookies based authentication and I'm just using a different URL while I'm in local development?

Run bench build after every change is not a good experience, what would be your advice in that case?

[sk-thakor]

in next js when i load intial time rendor so that time current user got undefined insted of in browser cookies already set. but if my page refresh so i got current user why this thing happen. this reason i haven't deside user login or not so intial rendor time login and signup i can but already set cookies so authenticaation fail. can anyone feze this issue so help for solving this issue why this thing happend and how can solve this