using the clientId and activeChain instead the desiredChainId

[alisonborba]

I was getting an error to fetch the contract:

query.ts:446 Error: Could not fetch bytecode for contract at 0x3cEeEbd92D12345678901234567890 on chain 1, double check that the address and chainId are correct.

And consequently got the error on creating a campaign: error TypeError: Cannot read properties of undefined (reading 'call').

This merge request solves the problem using the activeChain and clientId (got at https://thirdweb.com/dashboard/settings) instead of the desiredChainId on .

[jayanthpwr]

Thanks for the help, king!

[rahulsingh-99]

But I'm still getting errors that goerli is not supported on chains

[jayanthpwr]

Yes, Goerli was deprecated for test networks in 2023. I switched to Sepolia and altered the activeChain of main.jsx file accordingly to "sepolia"

[rahulsingh-99]

Can you give me the code because I tried every single thing but I'm still getting that error

[jayanthpwr]

I'm unable to do so, as I don't have the write access. You can refer what @alisonborba has done and enter sepolia instead with your personal Thirdweb clientId

[rahulsingh-99]

@alisonborba help me man I did not get any solutions after doing this activeChain and chainId I still getting this Could not fetch bytecode for contract at error

[jayanthpwr]

You can refer your clientID of your contract from this URL: https://thirdweb.com/dashboard/settings/api-keys
Then put in activeChain="sepolia".
If you're still preferring Goerli, I think the error may persist.

[rahulsingh-99]

Still facing the same issue

[RathoreAbhiii]

Still facing the same issue

It's not 'chainId'. Replace it with clientId='your_client_id'.