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

[nuxt] Could not access then. The only available runtime config keys on the client side are public and app #927

Open
1 of 4 tasks
gabriel-nigro opened this issue Oct 16, 2024 · 5 comments
Labels
bug A bug that needs to be resolved needs-reproduction Action needed: A valid reproduction of the issue needs to be added

Comments

@gabriel-nigro
Copy link

gabriel-nigro commented Oct 16, 2024

Describe the feature

I'm using Sidebase Nuxt-Auth + Nuxt3 + Vuetify3, and I'm getting this annoying warning when I click on the logout button, which calls signOut function.

Environment

❯ npx nuxi info
[17:08:40] Working directory: /home/projects/github-dvjyh3
[17:08:40] Nuxt project info:


  • Operating System: Linux
  • Node Version: v18.20.3
  • Nuxt Version: 3.13.2
  • CLI Version: 3.14.0
  • Nitro Version: 2.9.7
  • Package Manager: [email protected]
  • Builder: -
  • User Config: -
  • Runtime Modules: -
  • Build Modules: -

Reproduction

Link to stackblitz.

Just go to /login page and sign in. Right before you'll be redirected to /home, which have sign out button. Open console and click the button.

Provider

  • AuthJS
  • Local
  • Refresh
  • New Provider

Logs

Warning in Console:

[nuxt] Could not access then. The only available runtime config keys on the client side are public and app. See https://nuxt.com/docs/guide/going-further/runtime-config for more information.

@gabriel-nigro gabriel-nigro added enhancement An improvement that needs to be added pending An issue waiting for triage labels Oct 16, 2024
@phoenix-ru phoenix-ru added bug A bug that needs to be resolved needs-reproduction Action needed: A valid reproduction of the issue needs to be added and removed enhancement An improvement that needs to be added pending An issue waiting for triage labels Oct 17, 2024
Copy link

Hello 👋

Please provide a reproduction for this issue 🙏

How can I create a reproduction?

Please use one of the following links to reproduce your issue.

Please ensure that the reproduction is as minimal as possible. This will allow us to isolate the issue as best as possible.

Here are some more amazing posts about the importance of reproductions:

@andrescellini
Copy link

having same warning with both signIn and signOut methods using local provider

@gabriel-nigro
Copy link
Author

gabriel-nigro commented Oct 22, 2024

Hello 👋

Please provide a reproduction for this issue 🙏

How can I create a reproduction?

Here is the link: https://stackblitz.com/edit/github-dvjyh3

Just go to /login page and sign in. Right before you'll be redirected to /home, which have sign out button.

@DavidRoff
Copy link

I have this exact same problem and the signOut() call never completes, so neither the callbackUrl work or any code that would be executed after awaiting the signOut call.

@carvalhoms
Copy link

carvalhoms commented Nov 28, 2024

Hello, same issue here. I just created a new Nuxt application, imported nuxt-auth, and used the basic local provider setup as described in the documentation, but I'm encountering the same warning:

signIn() and signOut()

[nuxt] Could not access 'then'. The only available runtime config keys on the client side are 'public' and 'app'.

nuxt-auth 0.9.4

Has anyone figured out what’s causing this?

Will this cause issues in production?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug that needs to be resolved needs-reproduction Action needed: A valid reproduction of the issue needs to be added
Projects
None yet
Development

No branches or pull requests

5 participants