Skip to content

Files

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Latest commit

fa88ca1 · Feb 4, 2025

History

History
146 lines (141 loc) · 4.64 KB

2_bug_provider.yml

File metadata and controls

146 lines (141 loc) · 4.64 KB
NameAboutLabelsAssignees
Bug report (Provider)Create a provider-specific reporttriage,bug,providers

NOTE: Issues that are potentially security related should be reported to us by following the Security guidelines rather than on GitHub.
Thanks for taking the time to fill out this Provider related issue!
Is this your first time contributing? Check out this video: https://www.youtube.com/watch?v=cuoNzXFLitc

Important ❗

Providing incorrect/insufficient information or skipping steps to reproduce the issue will result in closing the issue or converting to a discussion without further explanation.

If you have a generic question specific to your project, it is best asked in Discussions under the Questions category

Provider(s) this issue is related to

Run this command in your project's root folder and paste the result:

npx envinfo --system --binaries --browsers --npmPackages "{next,react,next-auth,@auth/*}"

Alternatively, you can manually gather the version information from your package.json for these packages: "next", "react" and "next-auth". Please also mention your OS and Node.js version, as well as the browser you are using.

A URL to a public github.com repository outside the next-auth org that clearly reproduces your issue. You can use our next-auth-example template repository to get started more easily

Describe us what the issue is and what have you tried so far to fix it. Add any extra useful information in this section. Feel free to use screenshots (but prefer code blocks over a picture of your code) or a video explanation.

Explain with clear steps how to reproduce the issue

Explain what should have happened instead of what actually happened