TypeError: Cannot destructure property 'user' of 'useContext(...)' as it is undefined.
A component read a context with no matching Provider above it.
of 'useContext(...)' as it is undefineduseContext(...) as it is undefined Meaning
useContext returns the default value (often undefined) when there’s no Provider in the tree. Provider placed too low, wrong context instance, or tests without the provider.
Common causes
- Provider missing or below the consumer
- Two different context objects (duplicate module)
- Tests rendering without the provider
⚡ Quick fix
- Wrap the tree with the Provider at the right level
- Export the context from one module
- Create a custom hook that throws a clear error when the context is missing
Detailed fix by platform
React
- jsx
export function useAuth() { const ctx = useContext(AuthContext); if (!ctx) throw new Error('useAuth must be used within <AuthProvider>'); return ctx; }
How to diagnose
- Provider — Is it above the component?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- createContext only works in Client Components Next.js: You're importing a component that needs createContext. It only works in a Client Component but none of its parents are marked with "use client"
- Flask app context RuntimeError: Working outside of application context.
- No QueryClient set Error: No QueryClient set, use QueryClientProvider to set one
Most viewed in React
- React must be in scope ReferenceError: React is not defined / 'React' must be in scope when using JSX
- Objects are not valid as a React child Error: Objects are not valid as a React child
- Functions cannot be passed Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 14 Oct 2026