frappe / frappe/frappe-react-sdk
The useFrappeAuth() hook's currentUser remains undefined even after successful login
- Dominant language
- TypeScript
- Stars
- 189
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the useFrappeAuth() hook and the frappeLogin() flow to see why successful login does not update currentUser or set session cookies. Verify the behavior after login and on page refresh. Done means authentication state is maintained, currentUser is populated, session restoration works, and cookies are set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100