Describe the bug
When running the web app with pnpm dev, the app gets stuck on the guest login page and never reaches the home page.
The browser is redirected to:
/guest-login?callbackUrl=%2F
The terminal shows:
GET /guest-login?callbackUrl=%2F 200
It looks like the guest login flow does not successfully create a browser session in web-only dev mode. A direct request to /api/auth/guest redirects back to /, but the browser still ends up on /guest-login.
To Reproduce
Steps to reproduce the behavior:
- Clone the repository.
- Install dependencies:
- Start the web app:
- Open the local app in a browser:
- The browser redirects to:
/guest-login?callbackUrl=%2F
- The page keeps loading and never reaches the home page.
Expected behavior
pnpm dev should either successfully create a guest session and redirect to /, or clearly document that local development should use pnpm tauri:dev instead.
Screenshots
Not available.
Desktop
- OS: Windows
- Browser: Chrome / Edge
- Node.js: v20.20.2
- pnpm: 10.14.0
- App URL:
http://127.0.0.1:3515
Smartphone
Not applicable.
Additional context
The issue seems specific to the web-only dev path started by pnpm dev.
pnpm tauri:dev may avoid this because it uses the Tauri desktop runtime and a different local auth/token flow.
Describe the bug
When running the web app with
pnpm dev, the app gets stuck on the guest login page and never reaches the home page.The browser is redirected to:
The terminal shows:
It looks like the guest login flow does not successfully create a browser session in web-only dev mode. A direct request to
/api/auth/guestredirects back to/, but the browser still ends up on/guest-login.To Reproduce
Steps to reproduce the behavior:
Expected behavior
pnpm devshould either successfully create a guest session and redirect to/, or clearly document that local development should usepnpm tauri:devinstead.Screenshots
Not available.
Desktop
http://127.0.0.1:3515Smartphone
Not applicable.
Additional context
The issue seems specific to the web-only dev path started by
pnpm dev.pnpm tauri:devmay avoid this because it uses the Tauri desktop runtime and a different local auth/token flow.