nextauthjs / nextauthjs/next-auth

MissingSecret SvelteKit Template

Open
#7,380 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

svelte triage
Dominant language
TypeScript
Stars
28.4k
Forks
4k
PR merge metrics
No merged PRs in 30d

Description

Environment

Github online editor,
Deployed on Vercel

Reproduction URL

https://github.com/nextauthjs/sveltekit-auth-example

Describe the issue

I am using the template, only changed the .env to have secrets and changed the kit version to ^1.5.0
I am constantly getting the error i am MissingSecret even though all 3 of the standard secrets are filled and valid.
I am not able to find any topic on this or solution.

How to reproduce

Fork the template
Fill .env
Change package.json kit version from latest to ^1.5.0
Deploy to vercel

Expected behavior

Continuous failing with error MissingSecret.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SvelteKit example at the reproduction URL and compare its .env values with the deployment configuration on Vercel. Review the package.json change to Kit ^1.5.0 and trace when MissingSecret is reported. Done means the fork deploys without the MissingSecret error when the three documented secrets are set.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.