Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.70 Resolved a Big Issue (NEXTAUTH_URL) - Thank You! #708

Closed
lspellman-opsguru opened this issue Mar 8, 2024 · 1 comment
Closed

0.70 Resolved a Big Issue (NEXTAUTH_URL) - Thank You! #708

lspellman-opsguru opened this issue Mar 8, 2024 · 1 comment

Comments

@lspellman-opsguru
Copy link

Environment

Just wanted to give a quick shoutout for something 0.70 fixed.

I've been using 0.67 with a Nuxt 3 app and been banging my head against the wall for a few days where deployment to AWS Amplify was blocked by the NEXTAUTH_URL environment variable problem. For others who are researching this kind of problem, the issue is that you do not have control (i.e. can't set) any runtime environment variables for the "server" Amplify deploys with your app.

Buried within next-auth library is a call to process.env.NEXTAUTH_URL, that it can never retrieve. When it can't it sets the redirect_uri for Auth callbacks to http://localhost:3000 -- entirely blocking your production deployment!

I haven't dug into the internals to see what got changed with 0.70, but a vanilla deployment with whatever next-auth dependency it wants, works great. redirect_uri now picks up the domain host and callbacks from SignIn work.

Got lucky as I just happened to notice the release had been out there for 10 hours and decided to give it a whirl.

Many thanks! Close this ticket as soon as you'd like!

Reproduction

No repo needed

Describe the bug

No more bug :-) Joining as sponsor for solving my problem before you even knew I was having it, lol.

Additional context

No response

Logs

No response

@lspellman-opsguru lspellman-opsguru added bug A bug that needs to be resolved pending An issue waiting for triage labels Mar 8, 2024
@zoey-kaiser
Copy link
Member

Hi @lspellman-opsguru 👋

Thank you so much for your kind words! This issue completely went under, as you already had closed it, therefore I just noticed it ❤️

@zoey-kaiser zoey-kaiser removed bug A bug that needs to be resolved pending An issue waiting for triage labels Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants