fix: Change login in field.setValue to use optional operator

[smilingkylan]

Description

Login view attempts to reset the password input field value but sometimes the ref for the input field is null. Therefore, I have turned fieldRef.setValue to fieldRef?.setValue. Alternatively, since this occurs once successful navigation occurs and component is about to unmount, we may also be able to just remove the line.

Related issues

Addresses this Sentry issue: https://metamask.sentry.io/share/issue/ef784f4e764a4a76bc505dcdaa52c0ec/
GitHub issue: #12653

Manual testing steps

1. You can manually set the ref to null in the code and login to the app. It should not trigger the catch clause right underneath it.

Screenshots/Recordings

n/a but can producer if necessary

Before

n/a

After

n/a

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: 8d2c748
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/96f277d7-5744-4506-8687-0cf60abdebed

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

See analysis details on SonarQube Cloud