Moralis giving cors policy error after WalletConnect v2 update

Technical Issue Reporting
#1

Hello,

After the WalletConnect v1 was closed I updated the project with the code update in your https://github.com/MoralisWeb3/Moralis-JS-SDK-v1/tree/main/demos/walletconnect-v2 link. However, after this code, when I want to communicate with any SmartContract using fetch code from useWeb3ExecuteFunction in react-moralis library, I constantly get the following error;

Access to XMLHttpRequest at 'https://speedy-nodes-nyc.moralis.io/WalletConnect/bsc/mainnet' from origin 'https://app.intelly.tech' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Iā€™ve read other posts on the forum, but havenā€™t been able to find the right solution. Can you help me?

Note: My projectā€™s database is still on Moralis and Iā€™m still using moralis-v1.

#2

Hi, this might happen when you hit the rate limit. To avoid errors like this you can add your own node in the configs

#3

What is rate limit? How do I find out how much Iā€™ve used? Is it calculated monthly or daily? When I auth with metamask through the browser, I have no problems. But why canā€™t I run the same smartcontract functions when I auth with walletconnect?

PS: I only have this info in moralis panel: ā€œ99.99% CU Remainingā€. I am a pro plan user on moralis.

#4

It isnā€™t really a rate limit issue, the rate limit is per minute, that wallet connect endpoint is limited to work only for auth now, not also for smart contract interactions.

If you replace the RPC url with a different RPC url, even a public one, then it may work to also call smart contract functions.