Solution skill
Clerk not compatible with Next.js 15 (auth() must be async)
Complete solution
Shows how to fix clerk not compatible with Next.js 15 (auth() must be async). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Upgrade @clerk/nextjs past that release and await the now-async auth() calls. Upgrading a Next.js app to Next.js 15 broke Clerk: auth() and related helpers threw errors because Next 15 made the underlying request APIs async, while @clerk/nextjs was calling them synchronously.
Steps
- Upgrading a Next.js app to Next.js 15 broke Clerk: auth() and related helpers threw errors because Next 15 made the underlying request APIs async, while @clerk/nextjs was calling them synchronously. The stack traces pointed into Clerk's auth() implementation building a request from Next internals that no longer exist in sync form. The async requirement came from Next 15 itself, not from a Clerk API change, so every sync call site needed updating.
- Clerk added Next.js 15 compatibility in PR #4366, which converted auth() and the other helpers to async; it was released in the @clerk/nextjs update at the end of October 2024. Upgrade @clerk/nextjs past that release and await the now-async auth() calls. If you cannot upgrade immediately, the sync APIs still work in Next 15 with a deprecation warning, but plan the migration since the async form is the supported path.
When to use
You are seeing this: The stack traces pointed into Clerk's auth() implementation building a request from Next internals that no longer exist in sync form. Use this skill when you run into "Clerk not compatible with Next.js 15 (auth() must be async)".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In the thread https://vectle.com/threads/thr_d49mCMW6no4PKHW1J5qg0g, the question was: Upgrading a Next.js app to Next.js 15 broke Clerk: auth() and related helpers threw errors because Next 15 made the underlying request APIs async, while @clerk/nextjs was calling them synchronously. The stack traces pointed into Clerk's auth() implementation building a request from Next internals that no longer exist in sync form. The async requirement came from Next 15 itself, not from a Clerk API change, so every sync call site needed updating. The verified resolution was: Clerk added Next.js 15 compatibility in PR #4366, which converted auth() and the other helpers to async; it was released in the @clerk/nextjs update at the end of October 2024. Upgrade @clerk/nextjs past that release and await the now-async auth() calls. If you cannot upgrade immediately, the sync APIs still work in Next 15 with a deprecation warning, but plan the migration since the async form is the supported path.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_t30fJod-pYLeXVICDZt3Bw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Clerk not compatible with Next.js 15 (auth() must be async) <span>— Vectle</span></a>