VK provider not working

[degibons]

Provider type

Vk

Environment

  System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 AMD Ryzen 5 2600 Six-Core Processor
    Memory: 5.75 GB / 15.93 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.15.6 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.3570.0), Chromium (127.0.2651.74)
    Internet Explorer: 11.0.19041.3570
  npmPackages:
    @auth/prisma-adapter: ^2.4.2 => 2.4.2
    next: 14.2.5 => 14.2.5
    next-auth: ^5.0.0-beta.20 => 5.0.0-beta.20
    react: ^18 => 18.3.1

Reproduction URL

https://github.com/degibons/authjs-vk-issue

Describe the issue

When trying to sign in through a VK provider, an error is displayed
{"error":"invalid_request","error_description":"Code challenge method is unsupported"}

How to reproduce

• Clone the repository from Reproduction URL and run npm install
• Create and setup vk app https://id.vk.com/about/business/go
• Create .env file from .env.example
• Fill AUTH_VK_ID, AUTH_VK_SECRET variables from created vk app
• Run docker db container npm run db
• Push db schema npx prisma db push
• Run dev app npm run dev
• Go to localhost and click the button "SignIn"

Expected behavior

Normal sign in flow without this error.

[github-actions]

This issue was marked with the good first issue label by a maintainer.

This means that it is a good candidate for someone interested in contributing to the project, but does not know where to start.

Have a look at the Contributing Guide first.

This will help you set up your development environment to get started. When you are ready, open a PR, and link back to this issue in the form of adding Fixes #1234 to the PR description, where 1234 is the issue number. This will auto-close the issue when the PR gets merged, making it easier for us to keep track of what has been fixed.

Please make sure that - if applicable - you add tests for the changes you make.

If you have any questions, feel free to ask in the comments below or the PR. Generally, you don't need to @mention anyone directly, as we will get notified anyway and will respond as soon as we can)

Note

There is no need to ask for permission "can I work on this?" Please, go ahead if there is no linked PR 🙂

[rhiskey]

Same issue. Seems like provider errors and inner VK API refactoring. I suppose this bug needs to be addressed not to Auth.js developers but to vk itself.