fix: invoke_snap RPC requests inside the built-in browser

[Prithpal-Sooriya]

Description

BUG:
The invoke_snap RPC calls kept failing, returning a RPC Error: Property 'handleSnapRequest' doesn't exist.

FIX:
The handleSnapRequest import was code-fenced as part of the keyring snap, but should be available to all snaps. I moved the relevant import outside of the codefence.

Related issues

Fixes: https://infura.atlassian.net/issues/MDD-117 / https://consensys.slack.com/archives/C027M10HGEA/p1736428038068929

Manual testing steps

1. Visit this preview in the MM browser: https://metamask-docs-git-snap-debugging-branch-consensys-ddffed67.vercel.app/developer-tools/faucet/
2. (optional) Press the "Debug Test" button, it should complete
3. Press the "Connect MetaMask" button, it should complete

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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 format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). 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.

[github-actions]

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.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 59.72%. Comparing base (9d6908b) to head (6e12d2a).
Report is 58 commits behind head on main.

Files with missing lines	Patch %	Lines
app/core/Engine/Engine.ts	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12923      +/-   ##
==========================================
+ Coverage   58.85%   59.72%   +0.86%     
==========================================
  Files        1851     1865      +14     
  Lines       41739    42017     +278     
  Branches     5397     5458      +61     
==========================================
+ Hits        24566    25093     +527     
+ Misses      15502    15245     -257     
- Partials     1671     1679       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 80be0b0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/780f1371-d7dc-4a5b-bf16-cb874034ee74

Note

• This comment will auto-update when build completes
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 42d72bb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d9524322-3828-4240-baac-bd5bd75af726

Note

• This comment will auto-update when build completes
• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 27e7cf4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f8557afd-0e22-40a1-aa80-2fe720392e20

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[NicolasMassart]

Looks good to me.