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

[bug] Vercel Deployment fails even though project ID defined. #2260

Closed
1 task done
Patrick-Ehimen opened this issue Dec 8, 2024 · 2 comments
Closed
1 task done

Comments

@Patrick-Ehimen
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

RainbowKit Version

2.1.5

wagmi Version

2.12.8

Current Behavior

I have a Nextjs14 project, and my WalletConnectId variable is populated within an .env variable but only works with localhost. When trying to build with vercel, the error shows up.

'Error: No projectId found. Every dApp must now provide a WalletConnect Cloud projectId to enable WalletConnect v2'

Expected Behavior

Build should not fail.

Steps To Reproduce

To Reproduce
Steps to reproduce the behavior:

  1. Create NextJS 14 project
  2. Create .env in root directory
  3. Declare project ID variable with process.env.NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID
  4. Use wagmi or Rainbow kit to create providers
  5. Deploy project to github amd when Vercel tries to build project the build fails with the error

"Error: No projectId found. Every dApp must now provide a WalletConnect Cloud projectId to enable WalletConnect
v2"

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

No response

Copy link

linear bot commented Dec 8, 2024

@DanielSinclair
Copy link
Collaborator

It sounds like you just need to add NEXT_PUBLIC_WALLET_CONNECT_PROJECT_ID to your Vercel deployment env variables via their dashboard or CLI. https://vercel.com/guides/how-to-add-vercel-environment-variables

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