Update wallet connect CSP configuration #793
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alvarengathomas
approved these changes
Jan 28, 2025
gabmontes
approved these changes
Jan 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Staging (and prod) are showing the following errors
It seems after we updated Wagmi and viem, new URLs were added for connecting to WalletConnect. This is regardless of the secrets for Wallet Connect being enabled or not (which they're not yet).
This PR generalizes the domain URLs for WalletConnect so they are allowed in CSP. I couldn't find any
https://*.walletconnect.comrequest, so I did not add itScreenshots
Related issue(s)
Related to #633
Checklist