fix: ledger singing on re-designed signature pages

[jpuri]

Description

In new designs app was hanged after any error in ledger signing. The PR fixes this issue.

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/4482

Manual testing steps

1. Connect to ledger
2. On test dapp submit signatures
3. Ensure they works as expected

Screenshots/Recordings

TODO

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.

[sleepytanya]

QA builds: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2af8fa73-3387-408c-8d9e-585721ca8462

Personal Sign, Sign Typed Data v4 and Sign Permit work on iOS and Android.
iOS

ios.mov

Android

android.mp4

Sign with Ledger text is not fully visible:

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: c386f43
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4b651b6a-69de-4ef8-ad05-96cccd9c091e

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
66.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud