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

Wrong network is displayed on the delete CF safe pop up dialog #4379

Open
liliya-soroka opened this issue Oct 15, 2024 · 1 comment · May be fixed by #4589
Open

Wrong network is displayed on the delete CF safe pop up dialog #4379

liliya-soroka opened this issue Oct 15, 2024 · 1 comment · May be fixed by #4589
Assignees
Labels
bug Something isn't working multichain

Comments

@liliya-soroka
Copy link
Member

liliya-soroka commented Oct 15, 2024

Bug description

Wrong network is displayed on the delete CF safe pop up dialog

Environment

  • Browser: Chrome
  • Wallet: MetaMask
  • Chain: Ethereum mainnet

Steps to reproduce

  1. Open Polygon safe from the group of safes
  2. Add CF safe on Scroll to the group
  3. Switch you connected EOA to sepolia
  4. Go to theMy accounts
  5. try to delete Scroll CF from the group
    Current result : The polygon is displayed in the delete confirmation pop up

Expected result

Make sure that correct network is displayed in the pop up

Obtained result

Screenshots

Screen.Recording.2024-10-15.at.13.20.48.mov
@liliya-soroka liliya-soroka added the bug Something isn't working label Oct 15, 2024
@github-project-automation github-project-automation bot moved this to New issues in Web Squad Oct 15, 2024
@liliya-soroka
Copy link
Member Author

15.11.24

@schmanu schmanu moved this from New issues to In Progress in Web Squad Dec 2, 2024
@schmanu schmanu self-assigned this Dec 2, 2024
@schmanu schmanu linked a pull request Dec 2, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working multichain
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

4 participants
@liliya-soroka @schmanu @usame-algan and others