fix: add source when local PPOM fails

[vinistevam]

Description

This PR fixes an issue where the source property was not being set correctly when an error occurred during local PPOM validation. Previously, if the local PPOM failed, the error handling mechanism would add an error message but omit the source property, making it unclear whether the error originated from the API or the local PPOM.

Changes introduced:

• Modified error handling for the local PPOM validation to ensure that the source property is correctly set to "local" when an error occurs during local validation.
• Ensured that the source property is properly set to "api" in case of an API failure.

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/2058

Manual testing steps

1. Go to the live test dapp
2. Trigger a send transaction with suggested gas values (ie Send Legacy or send EIP1559)
3. Check Segment

Obs: We need to block the network calls for https://security-alerts.api.cx.metamask.io/ and https://static.cx.metamask.io/api/v1/confirmations/ppom/ppom_version.json in the Chrome dev tools > network tab.

Screenshots/Recordings

security-alerts-local.webm

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.

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 7a47ee4
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/997692e3-7d64-4a22-adec-414258cc5de8

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 5d56ed5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/50915e5d-0541-4c71-8d21-8b5b88da1d7b

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

[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