const walletConnect = walletConnectModule({
projectId: 'ourProjectId', // it's failing even with hardcoded string
version: 2,
dappUrl: 'ourUrl',
})
When running app locally everything works as expected. Once deployed to staging / prod environment projectId is missing in query as in example below and therefore it's impossible to connect a wallet.
If we downgrade walletconnect package version to 2.4.6 everything works as expected.
Weirdly enough a request before request mentioned above contains project id and returns 200.
https://verify.walletconnect.org/ourProjectId
Expected Behavior
Wallet connection working on package version above 2.4.6
Steps To Reproduce
Use Next.js app. Prep config in the way described above. Deploy it somewhere and try to use wallet connect modal.
What package is effected by this issue?
@web3-onboard/walletconnect": "2.5.3
Is this a build or a runtime issue?
Runtime
Package Version
2.5.3
Node Version
18
What browsers are you seeing the problem on?
Chrome
Relevant log output
{"error":"Missing projectId query parameter"}
Anything else?
No response
Sanity Check
[X] If this is a build issue, I have included my build config. If this is a runtime issue, I have included reproduction steps and/or a Minimal, Reproducible Example.
Current Behavior
Config:
When running app locally everything works as expected. Once deployed to staging / prod environment
projectId
is missing in query as in example below and therefore it's impossible to connect a wallet.If we downgrade walletconnect package version to 2.4.6 everything works as expected.
Weirdly enough a request before request mentioned above contains project id and returns 200.
https://verify.walletconnect.org/ourProjectId
Expected Behavior
Wallet connection working on package version above 2.4.6
Steps To Reproduce
Use Next.js app. Prep config in the way described above. Deploy it somewhere and try to use wallet connect modal.
What package is effected by this issue?
@web3-onboard/walletconnect": "2.5.3
Is this a build or a runtime issue?
Runtime
Package Version
2.5.3
Node Version
18
What browsers are you seeing the problem on?
Chrome
Relevant log output
Anything else?
No response
Sanity Check