I’m having trouble with my Next.js app using Thirdweb. When I try to use my contract, I get an error saying ‘Contract is not a nft-drop’. I’ve tried copying the exact code from the Thirdweb dashboard, but no luck. Here’s what I’m using:
import { useContract } from '@thirdweb-dev/react'
function NFTDropComponent() {
const { contract } = useContract('0x1234...5678', 'nft-drop')
// More code here to use the contract
}
I’m following the Thirdweb React docs, but it’s still not working. Any ideas on how to fix this? Maybe I’m missing something obvious? I’m pretty new to NFTs and smart contracts, so any help would be awesome!
hey ava, sounds frustrating! have u double-checked ur contract type in thirdweb dashboard? sometimes contracts are actually ‘edition-drop’ or ‘nft-collection’ instead of ‘nft-drop’. try using the generic useContract hook first without specifying type, might help pinpoint the issue. good luck!
hey there Ava61! i’ve been tinkering with thirdweb lately too and ran into similar headaches. have you considered that maybe the contract isn’t actually an nft drop? sometimes it’s easy to mix up the different contract types
what if you try using the useContract hook without specifying the type first? like this:
const { contract } = useContract('0x1234...5678')
you could then check what type of contract it actually is. also, silly question but are you sure you’re on the right network? i’ve def made that mistake before lol
btw, what kind of nft project are you working on? sounds interesting! always curious to hear about new ideas in the space
I’ve seen this issue before. It often happens when the contract address doesn’t actually match an NFT Drop but is being used as one. It might be that the contract wasn’t deployed as an NFT Drop, or it could be a network mismatch issue, so double-checking the address against a blockchain explorer can help confirm its type. Testing with the generic useContract hook could narrow it down, ensuring that you’re connected to the correct network before re-specifying the type.
