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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Wallet API - When I'm conneting to the test dapp for the first time, I'm switched to Mainnet automatically, despite not having this network selected #27891

Open
seaona opened this issue Oct 16, 2024 · 2 comments · May be fixed by #27980
Open

[Bug]: Wallet API - When I'm conneting to the test dapp for the first time, I'm switched to Mainnet automatically, despite not having this network selected #27891

seaona opened this issue Oct 16, 2024 · 2 comments · May be fixed by #27980
Labels
regression-develop Regression bug that was found on development branch, but not yet present in production regression-RC-12.7.0 release-12.6.0 Issue or pull request that will be included in release 12.6.0 release-blocker This bug is blocking the next release Sev2-normal Normal severity; minor loss of service or inconvenience. team-wallet-api-platform team-wallet-ux type-bug

Comments

@seaona
Copy link
Contributor

seaona commented Oct 16, 2024 •
edited
Loading

Describe the bug

When I'm conneting to the test dapp for the first time, I'm switched to Mainnet automatically, despite not having this network selected.
This is not happening in current production, but it has changed recently (happening on develop, meaning it will appear in 12.7.0).
This also makes fail the snaps test very frequently for this reason, see here.

Expected behavior

Preserve my selected network, like we did before?

Screenshots/Recordings

See current behaviour (switched automatically) and production behaviour (preserving my selected network)

switched-to-not-selected-network.mp4

Steps to reproduce

  1. Select localhost network
  2. Go to the test dapp
  3. Click connect
  4. Connect
  5. See you are switched to Mainnet automatically

Error messages or log output

No response

Detection stage

On the development branch

Version

12.7.0

Build type

None

Browser

Chrome

Operating system

Linux

Hardware wallet

No response

Additional context

No response

Severity

No response
@seaona seaona added type-bug release-blocker This bug is blocking the next release labels Oct 16, 2024
@seaona seaona mentioned this issue Oct 16, 2024
Merged
7 tasks
@seaona seaona added the release-12.7.0 Issue or pull request that will be included in release 12.7.0 label Oct 16, 2024
@metamaskbot metamaskbot added the regression-develop Regression bug that was found on development branch, but not yet present in production label Oct 16, 2024
@seaona seaona added regression-RC-12.7.0 Sev2-normal Normal severity; minor loss of service or inconvenience. team-wallet-api-platform team-wallet-ux labels Oct 16, 2024
github-merge-queue bot pushed a commit that referenced this issue Oct 16, 2024
@seaona
fix: flaky test `Snap Account Signatures and Disconnects can connect …
bb2e2a9 
…to the Test Dapp, then #signTypedDataV3, disconnect then connect, then #signTypedDataV4 (async flow approve)` (#27887)

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
After connecting to the test dapp we are automatically switched to
Mainnet (this is a recent change, didn't happen before). Then there is a
race condition where the network the dapp sees is different from the
wallet one, causing a miss-match and making the signature fail never
opening the dialog.

This seems an issue on the wallet side, as we should preserve the
selected network after connecting, as we used to do before.

I've opened an issue for that
[here](#27891).

This just fixes the issue on the e2e side, but it needs to be fixed on
the wallet side and remove the extra step again once the issue is fixed.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/27887?quickstart=1)

## **Related issues**

Fixes: #27892

## **Manual testing steps**

1. Check ci


## **Screenshots/Recordings**
See how you are automatically switched to mainnet


https://github.com/user-attachments/assets/d8fa53f5-b207-46bc-8e54-073245eff7b7



## **Pre-merge author checklist**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@jiexi
Copy link
Contributor

jiexi commented Oct 18, 2024

In the first part of the reproduction when you are connecting, only mainnet and linea are selected. For ganache to remain the selected network for the dapp after connection, ganache must also be selected at the time of connection

@seaona
Copy link
Contributor Author

seaona commented Oct 18, 2024 •
edited
Loading

hey @jiexi , from the slack thread, the solution should be:

Feels like an easy win to add the currently selected network to the list of preselected networks. Also makes it seem less like a regression / more backwards compatible

@gauthierpetetin gauthierpetetin added release-12.6.0 Issue or pull request that will be included in release 12.6.0 and removed release-12.7.0 Issue or pull request that will be included in release 12.7.0 labels Oct 21, 2024
@NidhiKJha NidhiKJha linked a pull request Oct 23, 2024 that will close this issue
Open
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
regression-develop Regression bug that was found on development branch, but not yet present in production regression-RC-12.7.0 release-12.6.0 Issue or pull request that will be included in release 12.6.0 release-blocker This bug is blocking the next release Sev2-normal Normal severity; minor loss of service or inconvenience. team-wallet-api-platform team-wallet-ux type-bug
Projects
Bugs by severity
Status: To be fixed
Bugs by team
Status: To be fixed
Milestone
No milestone
4 participants
@jiexi @gauthierpetetin @metamaskbot @seaona