Edge runtime does not work inside route group

[alvarlagerlof]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sat Nov 26 16:55:13 UTC 2022
Binaries:
  Node: 16.16.0
  npm: 8.11.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.0.7-canary.4
  eslint-config-next: 13.0.6
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue

alvarlagerlof/portfolio#584

To Reproduce

Deploy the repo branch linked on Vercel, and open /about

Describe the Bug

A route inside of a route group like (main) fails with a 500 error in Vercel when using the Edge runtime, but works perfectly fine when moving it outside of the route group.

Expected Behavior

The page works inside the route group as it does outside.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

[alvarlagerlof]

Closing because the issue is the same as #43458

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.