Root cause: Trackers were using Redux state.auth.user (mock data) while insights page was using useAuth() hook (real backend data from /me). Since the user is logged in as andrei@cloudz.ro, AuthContext fetches the real user with Alice child, but trackers were looking for mock familyId 'fam_test123' which doesn't exist. Fix: Changed all tracker pages and home page to use: user?.families?.[0]?.familyId (from useAuth hook) instead of: state.auth.user?.familyId (from Redux mock) This makes all pages consistent with the insights page approach. Files updated: - app/page.tsx (home) - app/track/sleep/page.tsx - app/track/feeding/page.tsx - app/track/diaper/page.tsx - app/track/activity/page.tsx - app/track/growth/page.tsx - app/track/medicine/page.tsx Now all pages fetch children using the real logged-in user's familyId. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.