chore: dont poll requests if the client is locked #43
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.
4.11 Cronjob - Check if MetaMask Is Locked
Description
The cronjob handler calls RequestManager.poll() every 10 seconds. The poll() function access data from encrypted state via stateManager. According to the Snaps API Documentation, encrypted storage cannot be accessed while MetaMask is locked.
Note: The cronjob is running every minute. Due to the clients requirements their Snap polls for updates every 10 seconds. Therefore they install 6 promises every minute (10 seconds apart). This might lead to deferred promises triggering while MetaMask is locked.
Recommendation
Inside pollRequests return early, if snap_getClientStatus returns that MetaMask is locked.