Weird 404 Server Error When Using Grouped Layouts

[MattHeslington]

Hello,

I have a page in a grouped layout making a call to a simple api endpoint. When 'hello world' is returned to the page, I get the following error in the server console:

SvelteKitError: Not found: /src/routes/test/test/+page.svelte
    at resolve (/Users/Matt/Documents/WebApps/galaxy/_tests/test-fetch-og-no-hooks/node_modules/.pnpm/@sveltejs+kit@2.5.18_@sveltejs+vite-plugin-svelte@3.1.1_svelte@4.2.18_vite@5.3.4/node_modules/@sveltejs/kit/src/runtime/server/respond.js:522:13)
    at resolve (/Users/Matt/Documents/WebApps/galaxy/_tests/test-fetch-og-no-hooks/node_modules/.pnpm/@sveltejs+kit@2.5.18_@sveltejs+vite-plugin-svelte@3.1.1_svelte@4.2.18_vite@5.3.4/node_modules/@sveltejs/kit/src/runtime/server/respond.js:322:5)
    at #options.hooks.handle (/Users/Matt/Documents/WebApps/galaxy/_tests/test-fetch-og-no-hooks/node_modules/.pnpm/@sveltejs+kit@2.5.18_@sveltejs+vite-plugin-svelte@3.1.1_svelte@4.2.18_vite@5.3.4/node_modules/@sveltejs/kit/src/runtime/server/index.js:71:56)
    at Module.respond (/Users/Matt/Documents/WebApps/galaxy/_tests/test-fetch-og-no-hooks/node_modules/.pnpm/@sveltejs+kit@2.5.18_@sveltejs+vite-plugin-svelte@3.1.1_svelte@4.2.18_vite@5.3.4/node_modules/@sveltejs/kit/src/runtime/server/respond.js:319:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  status: 404,
  text: 'Not Found'
}

Bearing in mind this is the page I'm on and the page which is making the api call.

My folder structure is like this:

/routes
    /(test)
        /test
            +layout.svelte
            +page.svelte
    +page.svelte

It doesn't break anything, it's just annoying. Does anyone know what's causing this, please?

I have a minimal reproducable example (or whatever it's called) here:
GitHub Repo

Any help would be very, very much appreciated. I've spent hours on this trying to work out what's causing the problem after initally being convinced it was Supabase auth code which was causing it.

Many thanks,
Matt

[dopiotrek]

I'm also using groups and the SvelteKit error keeps pointing to a route that has public in it, but actually it is (public). Other than that, all works (but annoying af)

[MattHeslington]

Ah, so it's not just me then

[eltigerchino]

I can't seem to reproduce it locally or through stackblitz https://stackblitz.com/~/github.com/MattHeslington/sveltekit-404-bug

[dopiotrek]

I tried in hooks.server.ts to console log event properties (in authGuard) and got some discrepancies in the URLs while I accessed my /login page, which also was in a grouped layout

console.log('event.url:', event.url);
console.log('event.url.href:', event.url.href);
console.log('event.url.pathname:', event.url.pathname);

Expected output:

event.url: URL {
  href: 'http://localhost:5173/auth/login',
  origin: 'http://localhost:5173',
  protocol: 'http:',
  // ... other
}
event.url.href: http://localhost:5173/auth/login
event.url.pathname: /auth/login

Fix (for now, seems to have worked)
Does not feel like a fix. SvelteKit expects to be served over HTTP, so I just prefixed localhost with HTTP://
(I thought it was by default opening over HTTP)

I am still looking, though, for code that modifies the pathname somewhere; I have not been able to identify it so far.