MissingSecret error during Next build since 5.0.0-beta.16 about next-auth

[hazamashoken]

Current workaround is to just set anything to AUTH_SECRET during build time and change the env variable again during runtime. But yea this is very annoying.

[SpectralAngel]

It is not even reading the secret while using npm next dev, the check for AUTH_SECRET should not be there until the app has been completely initialiazed, that means until the environment variables have been loaded (build time is bad for it also)

[balazsorban44]

Hi all,

Current workaround is to just set anything to AUTH_SECRET during build time

This would be my suggestion too. The reason for this is that some path in your code might be hit during prerendering (next build) that relies on auth. This will result in the AUTH_SECRET check invocation.

1. You can set it to a dummy value, just make sure that the production version has a properly set secret. You can use npx auth secret for example.
2. Or you can try to figure out what invoked authentication. The missing secret check is already a runtime check.

It is not even reading the secret while using npm next dev,

This sounds unrelated and something specific to your project. Next.js reads environment variables as a priority so they should always be available before the dev server is initialized. I cannot tell more without seeing your code, but it's most likely nothing to do with Auth.js.

[StuartMorris0]

I have the same issue with a turborepo project. AUTH_SECRET is set in an env file and is also included in turbo config.

It doesn't appear to be used. I presume pnpm dev is using the env.local and the pnpm build even when run locally is not using .env.local or not finding the value for some reason.

Rolling back to the previous beta version does resolve the issue for now

[StuartMorris0]

I don't think the issue is resolved just yet @balazsorban44

[balazsorban44]

Please open a new issue with a minimal reproduction then. Please don't give a full monorepo that takes a lot of time to set up, please strip it down to the bare minimum that still reproduces the issue, if the monorepo setup is even relevant. if it reproduces without one, please provide a simple repo isntead.

Saying that it's not resolved is not actionable.