Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId. #5389

Open
DDev16 opened this issue Nov 7, 2024 · 23 comments

Comments

@DDev16
Copy link

DDev16 commented Nov 7, 2024

Describe the bug
A clear and concise description of what the bug is.
i have been developing using UUPS upgradebale proxy pattern and mid upgrade remix got stuck. so i refrresehd the page and clear my activity on metmask. once i did this i then tried to interact with contracts and or upgrade my contracts and i get this error

No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Injected provider with Metamask'
  2. 'Chain ID 14'
  3. compile contract
  4. click deploy

then this error

No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.

Expected behavior
i need to interact with Flare EVM as i have for 5 years not sure whats going on

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [Windows 11]
  • Browser [edge]
  • Version [@latest]

Additional context
Add any other context about the problem here.

@DDev16
Copy link
Author

DDev16 commented Nov 7, 2024

@MDSL21
Copy link

MDSL21 commented Nov 8, 2024

Hi! I’m encountering a similar issue. I’m unable to interact with deployed functions on chain ID 97 (BSC testnet). Whenever I attempt to click on a public or simple external function, I receive the following error:

No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.

However, the issue disappears when I switch back to chain ID 56

Screenshot 2024-11-07 at 9 58 48 PM

@DDev16
Copy link
Author

DDev16 commented Nov 8, 2024

Yes I'm currently experiencing same issue, except for Chain id 14 (Flare) and chain 16 (Songbird)

if I switched to chain id 1 I have no issue and can interact with that network. Same for other EVM chains

I've been developing and working on UUPS Upgradeable contracts all day and all last night. this issue seemed to have happened mid day today while I was testing a contract.

I've had to resort to interacting with the contracts and performing upgrades via hardhat, ethers, and node.js with scripts

which sucks as i used remix for mainly testing with ease. hopefully this issue gets resolved.. ive noticed they had a recent fail on their recent push maybe that has something to do with it

@supmisterkim
Copy link

Also happens with chain ID 8453 (Base)

@junnai09
Copy link

junnai09 commented Nov 8, 2024

I am also experiencing this issue with Chain ID 8008135 (Fhenix Helium)

@ntop001
Copy link

ntop001 commented Nov 8, 2024

This is a weird problem, I have just deployed my contract few days ago, and the today, when I want to deploy a new one with another wallet, it's said:

No compatible chain found for the selected EVM version.
Consider opening an issue to update our internal store with your desired chainId.

Honestly,I don't know what happened, just don't work anymore.

@aayush2870
Copy link

I am experiencing the same issue in Remix. When attempting to deploy a contract on the Amoy network (chain ID: 80002), I receive the following error message:

"No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId."

Despite this message, I was able to deploy the contract. However, none of the functions in the contract are working after deployment.

@AuronCrow10
Copy link

AuronCrow10 commented Nov 8, 2024

Same here, a contract that worked perfectly fine untill few hours ago now gives me the following error message

"No compatible chain found for the selected EVM version. Consider opening an issue to update our internal store with your desired chainId."

Currently on Blast Sepolia, chainID: 168587773

@giirafe
Copy link

giirafe commented Nov 8, 2024

Same issue on Amoy Network(Chain ID:80002). In my case I was trying to access deployed contract using 'At Address' and this error occured

@Caneryy
Copy link

Caneryy commented Nov 8, 2024

I've been getting the same error since yesterday. Chain ID: 167009

@aiachain
Copy link

aiachain commented Nov 8, 2024

I've been getting the same error since today. Chain ID: 1319

@huahuahua1223
Copy link

I've been getting the same error since today. Chain ID: 1337

@RamirezXxX
Copy link

I have same error since today
No compatible chain found for the selected EVM version.

@devduru
Copy link

devduru commented Nov 8, 2024

Also happens with chain ID 8453 (Base)

yes just observed that now, any solution?

@yanyang729
Copy link

yanyang729 commented Nov 8, 2024

same problem different chain since today

@ketan-esp
Copy link

same issue with all chains

@lxh1121
Copy link

lxh1121 commented Nov 8, 2024

same problem ,bsc testnet chain ID 97。
image

@mehzee92
Copy link

mehzee92 commented Nov 8, 2024

Same issue for me on all chains i.e BSC, Bsc testnet, Sepolia etc

@fragtex-eth
Copy link

Same issue for me (ChainId: 1301)

@hoshi2237
Copy link

I encountered the same problem with Remix when I tried to deploy the contract on Ganache's local blockchain and received the message. However, trying to change the EVM version on Remix did not solve the problem. However, contract deployment can be carried out normally on Sepolia testnet.

@userInner
Copy link

我在使用FISCO-BCOS WEB3 RPC接口时,也报了相同错误,如下图
image

@DDev16
Copy link
Author

DDev16 commented Nov 9, 2024

its fixed everyone

@MDSL21
Copy link

MDSL21 commented Nov 10, 2024

its fixed everyone

Great! Everything is normal here now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests