Quickstart
- Knowledge Base
  - Introduction
  - Get support
Connect
- FAQs
  - Auth FAQ
  - Account Abstraction FAQ
  - In-App Wallets FAQ
  - Connect FAQ
Contracts
- FAQs
  - Explore FAQ
  - Publish FAQ
  - Build FAQ
  - Deploy FAQ
  - Interact FAQ
- How To
  - Claim from drop contract using contract explorer
  - Importing non-thirdweb contracts into the Dashboard
  - Airdrop Contract Troubleshooting
  - Trouble Claiming from the Embed
  - Customizing the Embed
  - Batch Upload Troubleshooting
  - Transferring ownership of a contract
  - How to close Auction Listings in a Marketplace
  - Take a Snapshot of Existing Holders
  - openPack Function out of gas
  - NFT Drop claim function parameters
  - NFT metadata structure
  - WalletConnect Prefab Required for Connect Wallet (Native) Prefab
  - How to use the multicall() function
  - Start Token ID at 1 instead of 0
  - Why can’t I claim an NFT from the embed on mobile?
  - Where can I see the audited contract reports?
  - How can I get my NFTs to show up on OpenSea or other marketplaces?
  - What are Platform Fees?
  - Why am I unable to use the same token for staking and rewards?
  - Understanding gas, Gwei, and cost saving strategies
  - How to make your NFTs non-transferrable aka Soulbound
  - SetApprovalForAll: what it means to grant access to all your NFTs
  - Staking Contract Troubleshooting - Not Owned or Approved
  - Token showing “Mintable” on dex scanner after renouncing
  - When will my collection show up on OpenSea?
  - My Collection is Not Showing Up
  - My Collection is Not Showing Up
  - NFTs Aren’t Revealing
Engine
- FAQs
  - Change my Engine admin (Cloud-hosted)
  - Using Engine as a relayer
  - Run Engine locally
  - Deploy Engine on Railway
  - Deploy contracts using OP Credits with thirdweb Engine
  - Unable to connect to Engine: Ensure that your Engine is publicly accessible
  - Cloud-hosted vs self-hosted Engine
  - Error: DEPTH_ZERO_SELF_SIGNED_CERT (Self-hosted)
Infra
- FAQs
  - RPC
  - Storage
- How To
  - Blockscout API contract verification
  - Token verification on Etherscan
  - Blockscout API contract verification
  - Token verification on Etherscan
General thirdweb Issues
- FAQs
  - Billing
  - Security & Privacy
- React
  - How to display a custom token on ConnectButton
  - How to migrate read-only hooks from thirdweb v4 to v5
  - How to get the signer for connected wallet
- Javascript
  - How to generate a private key account using the thirdweb SDK
  - How to generate merkle root for airdrop contract using SDK
  - How to take a snapshot of an ERC721 collection
  - How to check if a provided address is a contract address or wallet address
  - How to verify a contract using thirdweb SDK
  - How to check if a contract is an ERC721/ERC1155/ERC20 contract
  - How to fetch contract metadata
  - How to retrieve tokenIds from the lazyMint method
  - How to shuffle items when lazy minting
  - How to get all tokenIDs in an NFT contract
- Others
  - How to resolve ENS address
  - How to resolve ENS avatar
  - How to resolve ENS name?
  - How to signature mint using the thirdweb v5 SDK
  - How to update NFT metadata for drop contract via thirdweb SDK
  - How to update NFT metadata for via NFT Collection/Edition Contract
  - How to distribute funds on spilt contract with explorer
  - How to Find NFTs by Owner for an NFT Drop Contract
  - How to add a contract to the thirdweb dashboard via code
  - How to update the metadata for multiple NFTs
  - How to find the contract address from your transaction hash after deploying a contract
  - How to upload a single NFT via thirdweb explorer?
  - How to secure your API Keys
  - How to transfer native tokens
  - How to add a custom RPC URL into your front-end, backend, or dashboard
  - How to add your EVM chain to thirdweb’s Chainlist?
Commonly Seen Onchain Errors
- Application errors
  - This action requires a connected wallet to sign the transaction. Please pass a valid signer to the SDK.
  - [ethjs-query] while formatting outputs from RPC
  - Unity Error: "Multiple precompiled assemblies with the same name Newtonsoft.Json.dll included on the current platform”
  - Unity SDK Error: this functionality is not yet supported on the current platform
  - How to share your console log errors
  - 401 Unauthorized
  - Unauthorized - You don't have permission to use this service
  - We are not able to process your request at this time. Please contact thirdweb support.
  - ERR_FAILED_413
- RPC Errors
  - Transaction underpriced
  - Replacement transaction underpriced / Replacement fee too low
  - Cannot estimate gas; transaction may fail or may require manual gas limit
  - Nonce too low: next nonce #, tx nonce #
  - Nonce too high
  - ErrorData: 0x
  - Execution reverted (-32000)
  - Invalid request (-32600)
  - Invalid params / Invalid arguments (-32602)
- Onchain Errors
  - AA21 didn’t pay prefund
  - Paymaster deposit too low
  - Invalid UserOperation signature or paymaster signature
  - Execution Reverted: !Tokens
  - Execution reverted: !QTY
  - Execution reverted: ST
  - Insufficient funds for gas * price + value / Insufficient funds for intrinsic transaction cost
  - Execution reverted: !BAL20
  - Execution reverted: !BALNFT
  - Execution reverted: proof claimed
  - Execution reverted: !ADMIN
  - Execution reverted: !CONDITION
  - Execution Reverted: Not within the sale window
  - Execution Reverted: !Amt Error
  - ERC20 - Transfer Amount Exceeds Allowance
  - Account 0x… is missing role 0x…
  - Execution reverted !V
- CLI Errors
  - npm ERR! syscall spawn git
  - Issue linking device on the authorization page via thirdweb cli
General
Payments
More

Trouble Claiming from the Embed

Fix the most common issues and claim NFTs from your embed

Last updated on October 19, 2022

If you’re having trouble claiming from the embed, you’ve come to the right place 😄

In this troubleshooting document, we’ll guide you through some of the issues you may be facing, and how you can fix them to claim NFTs from the embed 🚀

If you still experience an issue or these do not apply, please reach out to us in our Discord or at support@thirdweb.com.

General Troubleshooting

“Failed to claim drop” error

Check if the connected wallet has enough balance to claim the drop. Most often, this error is the result of insufficient funds in the connected wallet

The embed does not appear

Do not browse in incognito/private mode or disable cookies - the embed will not appear in those cases. Use regular browsing mode with cookies enabled.

Disable any browser extension that modifies the webpage such as translators, ad-blocker, or devtool extensions.

Embed takes abnormally long or doesn’t load

In this case, the RPC connecting your application to the blockchain may be limiting the load time. You can try creating your own dedicated RPC and adding that to your Embed configuration in the RPC Url field. This should resolve the issue in the embed preview below.

Drop is not ready to be claimed

Double-check to ensure your claim conditions are set up correctly.

Mobile Troubleshooting

Selecting Metamask opens the App store

We are currently implementing built-in solutions for this issue. The most plug-and-play option to improve this for mobile users is to use the src link within your embed code itself. You can redirect mobile users to this src link and the Metamask button should allow the wallet to connect.

Metamask is not in the wallet option

We pushed a fix for this on the newest versions of the embed. Please return to the Embed tab on the dashboard, recopy the embed code, and replace the embed code on your website.

Did this answer your question?

😞

😐

🤩

Airdrop Contract Troubleshooting Customizing the Embed