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

Cannot connect to Etherscan anymore #484

Open
jfschwarz opened this issue Jan 8, 2025 · 2 comments
Open

Cannot connect to Etherscan anymore #484

jfschwarz opened this issue Jan 8, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@jfschwarz
Copy link
Collaborator

Describe the bug
Up until very recently you could connect Etherscan to Pilot to capture calls encoded there. This no longer seems possible

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://etherscan.io/address/0x27d8bb2e33Bc38A9CE93fdD90C80677b8436aFfb#writeContract
  2. Open Pilot panel
  3. Click on Connect to Web3 button in Etherscan
  4. Select MetaMask in the modal

It's now connected to MetaMask.

Expected behavior
It should be connected to Pilot. This used to work (even though the button always said MetaMask).

@jfschwarz jfschwarz added the bug Something isn't working label Jan 8, 2025
@jfschwarz
Copy link
Collaborator Author

same problem on https://abi.ninja

@frontendphil
Copy link
Member

It works when I use Rabby. But, as you said, it won't when I have the MetaMask extension running. Maybe this also has something to do with our current issues connecting MetaMask... I'll put some more work into externalizing the route configuration and will then get back to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants