-
-
Notifications
You must be signed in to change notification settings - Fork 187
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: fix detecting NFTs after closing browser #4178
Merged
sahar-fehri
merged 9 commits into
main
from
fix/optimize-detect-nft-calls-when-browser-closed
Apr 23, 2024
Merged
fix: fix detecting NFTs after closing browser #4178
sahar-fehri
merged 9 commits into
main
from
fix/optimize-detect-nft-calls-when-browser-closed
Apr 23, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
7 tasks
bergeron
reviewed
Apr 17, 2024
7 tasks
legobeat
reviewed
Apr 22, 2024
bergeron
approved these changes
Apr 22, 2024
sahar-fehri
deleted the
fix/optimize-detect-nft-calls-when-browser-closed
branch
April 23, 2024 19:32
sahar-fehri
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Apr 23, 2024
## **Description** Once nftDetection is enabled by the user, the nftDetection controller will start polling data in the background every 3 min even if the user closes the metamask popup or the tab. We want to stop unnecessary polling when MM is closed in an attempt to reduce traffic. [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24026?quickstart=1) ## **Related issues** Related to: MetaMask/core#4178 ## **Manual testing steps** 1. Go to this page... 2. 3. ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] 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.
sahar-fehri
added a commit
to MetaMask/metamask-extension
that referenced
this pull request
Apr 24, 2024
Once nftDetection is enabled by the user, the nftDetection controller will start polling data in the background every 3 min even if the user closes the metamask popup or the tab. We want to stop unnecessary polling when MM is closed in an attempt to reduce traffic. [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/24026?quickstart=1) Related to: MetaMask/core#4178 1. Go to this page... 2. 3. <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> <!-- [screenshots/recordings] --> <!-- [screenshots/recordings] --> - [ ] I’ve followed [MetaMask Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] 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. - [ ] 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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explanation
This PR goes together with this extension PR MetaMask/metamask-extension#24162
We want to reduce third party calls for nft detection when a user has closed the MM popup/window.
To do that we are leveraging
stopNetworkRequests
andtriggerNetworkrequests
functions inside extension to eitherstop()
orstart()
the nft detection.While doing this fixed the following scenario:
1- User imports MM wallet
2- User enables nft detection toggle
3- User closes MM tab or popup
4- We are no longuer making calls to third party because we called stop() function on nftDetectionController.
It does not fix this scenario:
1- User imports MM wallet
2- User enabled nft detection toggle
3- User closes chrome all together
4- User reopens chrome without opening MM, and we notice that it is making calls in the background to third party even though MM is not open.
This behavior was happening because of a couple of reasons; the property
disabled
being set totrue
indefaultConfig
made the check on this line pass
core/packages/assets-controllers/src/NftDetectionController.ts
Line 480 in 1551844
and triggered the
start()
function (because the useNftDetection is true).I fixed this by having extension pass the
disabled
in the contructor rather than having thetrue
value hardcoded in the controller.I have also refactored the
onPreferencesStateChange
to have it make this checkSeparately.
When the user first opens the selectedAddress is '' because its also set in default config which, because of the
OR
statement triggered the code to also go into thestart()
References
Changelog
@metamask/assets-controllers
Checklist