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

fix: bump message signing snap to support portfolio automatic connections #27306

Closed
wants to merge 12 commits into from

Conversation

Prithpal-Sooriya
Copy link
Contributor

@Prithpal-Sooriya Prithpal-Sooriya commented Sep 20, 2024

Description

Bumps @metamask/message-signing-snap to 0.4.0 to allow portfolio to support automatic connections.

Open in GitHub Codespaces

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/NOTIFY-1136

Manual testing steps

This does not effect anything within the wallet.

Screenshots/Recordings

Before

After

Pre-merge author checklist

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.

@Prithpal-Sooriya Prithpal-Sooriya added the team-notifications Notifications team label Sep 20, 2024
@Prithpal-Sooriya Prithpal-Sooriya requested a review from a team as a code owner September 20, 2024 14:39
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

Copy link

socket-security bot commented Sep 20, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected] None 0 232 kB metamaskbot
npm/[email protected] None 0 667 kB colinmcd94

🚮 Removed packages: npm/@metamask/[email protected], npm/[email protected]

View full report↗︎

mathieuartu
mathieuartu previously approved these changes Sep 20, 2024
dovydas55
dovydas55 previously approved these changes Sep 20, 2024
mathieuartu
mathieuartu previously approved these changes Sep 20, 2024
dovydas55
dovydas55 previously approved these changes Sep 20, 2024
@Prithpal-Sooriya
Copy link
Contributor Author

This cannot be merged as there are e2e tests that are failing. Investigating.

@Prithpal-Sooriya Prithpal-Sooriya marked this pull request as draft September 26, 2024 14:42
@Prithpal-Sooriya
Copy link
Contributor Author

Converted to draft, as there is a e2e test that needs fixing, but I haven't got time to fix this anytime soon.

Copy link

sonarcloud bot commented Oct 15, 2024

FrederikBolding added a commit to MetaMask/core that referenced this pull request Oct 16, 2024
## Explanation

This PR fixes a rare problem that would occur when deleting a network
after a proxy in `SelectedNetworkController` has been garbage collected.
When this happens, `getProviderAndBlockTracker` will fail to find the
old network client ID and thus updating the network client ID for the
domain will fail.

This could be reproduced in an E2E test that would only fail on this
branch: MetaMask/metamask-extension#27306 which
enables `initialConnections` for a preinstalled Snap.
`initialConnections` adds a permission for an origin to connect to a
Snap which causes the `SelectedNetworkController` to register the
domain. My theory is that since the user has not accessed the origin in
question yet, the proxy may not be used and may be garbage collected. If
a network is deleted following that, an error occurs.

## Changelog

<!--
If you're making any consumer-facing changes, list those changes here as
if you were updating a changelog, using the template below as a guide.

(CATEGORY is one of BREAKING, ADDED, CHANGED, DEPRECATED, REMOVED, or
FIXED. For security-related issues, follow the Security Advisory
process.)

Please take care to name the exact pieces of the API you've added or
changed (e.g. types, interfaces, functions, or methods).

If there are any breaking changes, make sure to offer a solution for
consumers to follow once they upgrade to the changes.

Finally, if you're only making changes to development scripts or tests,
you may replace the template below with "None".
-->

### `@metamask/selected-network-controller`

- **Fixed**: Ensure that network client ID is updated before using it

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've highlighted breaking changes using the "BREAKING" category
above as appropriate
- [x] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes
@github-actions github-actions bot locked and limited conversation to collaborators Oct 17, 2024
@matteoscurati matteoscurati reopened this Oct 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
team-notifications Notifications team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants