fix: camera permission alert with settings access

[vinnyhoward]

Description

This pull request addresses an issue related to camera permissions during the initial wallet setup in the app. The improvement provides a better user experience for those who initially deny camera access but later wish to use the QR scanning functionality.

implemented a solution to improve the user experience when dealing with camera permissions:

1. Replaced the old alert with a new, informative message when users attempt to use the QR scanner after initially denying permission.

2. Added functionality to route users directly to their system settings to modify camera permissions.

3. Enhanced user experience by providing a clear path to enable necessary app functionality.

Related issues

Fixes: Issue #10642

Manual testing steps

1. Fresh install the MetaMask mobile app.
2. Complete the initial wallet setup.
3. Tap the QR scanner icon in the top right corner.
4. When prompted "MetaMask Would Like to Access the Camera", select "Don't Allow".
5. Attempt to use the QR scanner again by tapping the icon.
6. Verify that the new alert appears with options to cancel or open settings.
7. Test that the "Open Settings" option correctly routes to the system settings.
8. Enable camera permissions in settings and return to the app.
9. Confirm that the QR scanner now functions correctly.

Screenshots/Recordings

iOS

Before	After

Android

Before	After

Before

NA

After

NA

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.

[yanrong-chen]

Updated copy/design here

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 09e9241
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fd985995-ef9e-4c2a-938f-640bbecf2b05

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 58585af
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e04e5a35-9aa5-4be2-9a23-592124d38e2d

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

[EtherWizard33]

nice, approved!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[georgewrmarshall]

LGTM! PR description is a thing of beauty! One non-blocking comment to check with our content design team.

• Checked manual testing steps locally ✅

I noticed that once we have completed the steps the simulator will still not open the camera but I'm assuming that is expected behavior of the simulator

after.mov