Services Plugins FAQs

Returned values aren't valid MetaMask & Web3 & Wallet Connect Plugin for Bubble

Plugins
#1

Hi, I hope you are doing great.

I am trying to make a transition using metamask but getting a error.

web3_1_7_4.js:23 Uncaught (in promise) Error: Returned values aren’t valid, did it run Out of Gas? You might also see this error if you are not using the correct ABI for the contract you are retrieving data from, requesting data from a block number that does not exist, or querying a node which is not fully synced.

image
image1872×264 74.9 KB

Could you please check?

Thank you

#2

Hello @shanni.satlujwebsolu ,

Thanks for sharing the error and the screenshot — let’s walk through what could be causing this and how to troubleshoot it.

The error message you’re seeing:

Uncaught (in promise) Error: Returned values aren’t valid. Did it run Out of Gas?
You might also see this error if you are not using the correct ABI for the contract you are retrieving data from, requesting data from a block number that does not exist, or querying a node which is not fully synced.

This typically points to one of the following issues:

  1. Incorrect ABI (Application Binary Interface)
    Make sure the ABI you’re using in your plugin or Bubble setup exactly matches the smart contract deployed to the blockchain. Even a small difference (e.g. changed function name, parameter mismatch) will break the setup.

  2. Wrong contract address or network
    Double-check that you’re connected to the correct network (e.g., Ethereum Mainnet, Polygon, etc.) and using the right contract address.

  3. The contract method being called does not exist or is not public/view
    Ensure that the function you’re calling exists on the contract, and it’s a public/view function if you’re reading data (vs. writing).

  4. Node not synced or RPC endpoint issue
    If you’re using a custom RPC node (like Infura, Alchemy, etc.), make sure it’s working and fully synced. Try switching to another RPC node to test.

  5. Gas issues only apply to transaction (write) functions
    If you’re just trying to read data (not send a transaction), gas shouldn’t be an issue. If you are making a transaction, try increasing the gas limit slightly and make sure you have enough ETH for gas fees.

To continue troubleshooting, could you please provide the following?

  • A screenshot of the plugin element’s configuration (with the contract address, method, and ABI field visible if possible)
  • Screenshots of your workflow, se we can better understand your use case
  • A screen recording with the debug_mode=true and in Step-by-step mode, so we can better understand when and where does the error message appear.

Once we get this info, we’ll be able to pinpoint the cause more accurately and guide you on the next steps.

Looking forward to your reply!

Best regards,
Egor Smorodinov,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3

#3

Hi @shanni.satlujwebsolu ,

Just following up on this thread to check in with you.

Is this question still relevant on your end, and are you still experiencing the same MetaMask / Web3 error? Were you able to go through the suggestions from my previous message — such as verifying the ABI, confirming the contract address and network, and testing a different RPC node — and did any of those steps help or change the behavior?

If the issue is still persisting, feel free to share any updates along with the screenshots or workflow details I mentioned earlier. That information will help us better understand your setup and pinpoint the root cause.

Looking forward to your update and happy to assist further :+1:

Best regards,
Egor Smorodinov,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3