-
Notifications
You must be signed in to change notification settings - Fork 5k
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
[Bug]: [MV3] Loading a detected phishing page for the first time does not show the phishing page warning #16551
Comments
I still can reproduce @digiwand 's behaviour mentioned above on the branch you pointed out @segun. The issue is that the phishing list does not load completely. Steps to repro:
Some extra information, highlighted by @digiwand: we combine the 2 lists https://static.metafi.codefi.network/api/v1/lists/eth_phishing_detect_config.json and https://static.metafi.codefi.network/api/v1/lists/phishfort_hotlist.json of results. I noticed that for every pause event from the debugger , we are getting different elements from the list:
2022-11-22.15-14-41.mp4 |
@seaona Thanks. I'm now able to reproduce the bug and have a fix. |
**Pass in initial state to PhishingController and load the initialState from persisted state** In Manifest V3, there's need to 1. Persist phishingcontroller state 2. Load phishingcontroller from persistent state Thos PR makes sure state is loaded from persistent state and also abstracts out the checks required before updating the lists - BREAKING: - All the code bases using PhishingController should continue to work as expected - CHANGED: - We should call initialise before calling PhishingDetector controller. - ADDED: - Added `maybeUpdatePhishingLists` method so that controllers don't have to do the check logic anymore **Checklist** - [ ] Tests are included if applicable - [ ] Any added code is fully documented **Issue** Resolves MetaMask/metamask-extension#16551 Signed-off-by: Akintayo A. Olusegun <[email protected]>
**Pass in initial state to PhishingController and load the initialState from persisted state** In Manifest V3, there's need to 1. Persist phishingcontroller state 2. Load phishingcontroller from persistent state Thos PR makes sure state is loaded from persistent state and also abstracts out the checks required before updating the lists - BREAKING: - All the code bases using PhishingController should continue to work as expected - CHANGED: - We should call initialise before calling PhishingDetector controller. - ADDED: - Added `maybeUpdatePhishingLists` method so that controllers don't have to do the check logic anymore **Checklist** - [ ] Tests are included if applicable - [ ] Any added code is fully documented **Issue** Resolves MetaMask/metamask-extension#16551 Signed-off-by: Akintayo A. Olusegun <[email protected]>
**Pass in initial state to PhishingController and load the initialState from persisted state** In Manifest V3, there's need to 1. Persist phishingcontroller state 2. Load phishingcontroller from persistent state Thos PR makes sure state is loaded from persistent state and also abstracts out the checks required before updating the lists - BREAKING: - All the code bases using PhishingController should continue to work as expected - CHANGED: - We should call initialise before calling PhishingDetector controller. - ADDED: - Added `maybeUpdatePhishingLists` method so that controllers don't have to do the check logic anymore **Checklist** - [ ] Tests are included if applicable - [ ] Any added code is fully documented **Issue** Resolves MetaMask/metamask-extension#16551 Signed-off-by: Akintayo A. Olusegun <[email protected]>
@seaona observed refreshing the extension from
chrome://extensions
and then opening a URL detected as a phishing page will not show the phishing warning page.Looking into this, it appears that the blocklist may not finish loading when the user first lands on a detected phishing page.
Observe breakpoint hit when list has not finished loading (
eth-phishing-detect/src/detector
):Observe breakpoint when list is loaded.
Related Repos:
For some reason, I am only able to repro this issue on MV3 and not MV2.
The text was updated successfully, but these errors were encountered: