Not a valid protocol - wails://

[pavelbinar]

Preliminary Checks

• I have reviewed the documentation: https://clerk.com/docs
• I have searched for existing issues: https://github.com/clerk/javascript/issues
• I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
• This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction

I believe the description is sufficient - let me know if not

Publishable key

pk_test_ZmFpci1ib2JjYXQtNjUuY2xlcmsuYWNjb3VudHMuZGV2JA

Description

I am using `` after sign-up I am redirecting to /.

This was working fine untill recently when I start getting an error in the web console:

Clerk: Not a valid protocol. Redirecting to /

I run my web app in the context of https://wails.io/
that mean that my window.location = "wails://wails.localhost:34115"

It seems that the wails:// protocol is newly causing a problem. Here is probably the responsible code:

javascript/packages/clerk-js/src/utils/windowNavigate.ts

Line 7 in 40eb63b

console.warn('Clerk: Not a valid protocol. Redirecting to /');

Environment

Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm
  npmPackages:
    @clerk/clerk-react: ^4.30.3 => 4.30.3

[jescalan]

Thanks for bringing this up - it is a valid use case and we are looking into ways that we can allow custom protocols to be passed in here.

[pavelbinar]

Hi, thank you for confirming.

I think it might be a regression, because we had a working sign up and it just stopped working.

I know it is hard but can you please get me some estimate for fix. If you don't see it in any foreseeable future then we will need to find a workaround.

[pavelbinar]

Wow, a fix within hours 🎉
Thank you for giving it such priority.

Looking forward to seeing it in the release: ⌛ #3558

[clerk-cookie]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.