fix: fixed getStakingNavbar broken back and cancel buttons regression

[Matt561]

Description

This PR fixes a recently introduced regression that broke the "back" and "cancel" buttons when using getStakingNavbar(). This only impacted the staking views.

Related issues

• Ticket that introduced regression: Stake-884: Add more mobile pooled staking events
• PR that introduced regression: feat: STAKE-884 add more mobile pooled staking events #12651

Manual testing steps

Stake Input Screen (broken cancel navbar button)

1. Set MM_POOLED_STAKING_UI_ENABLED to true in .js.env
2. Click "Ethereum" from the token list (home screen)
3. Click on the "Stake" or "Stake more" button (the same can be tested for the unstake flow if you have ETH staked)
4. From the Staking Input View, click the "Cancel" button in the top-right corner.
5. You should be redirected to the previous screen (Ethereum details)

Stake Confirmation Screen (broken back navbar button)

1. Set MM_POOLED_STAKING_UI_ENABLED to true in .js.env
2. Click "Ethereum" from the token list (home screen)
3. Click on the "Stake" or "Stake more" button (the same can be tested for the unstake flow if you have ETH staked)
4. Enter a valid amount and press "Review" to view the stake confirmation screen.
5. Click the "back" button in the top-left corner in the navbar
6. You should be redirected to the previous screen (stake input screen)

Screenshots/Recordings

Before

getStakingNavbar-regression-fix-before.mov

After

getStakingNavbar-regression-fix-after.mov

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: 5c79582
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/e9832dbd-0bb0-4fcc-b0fa-b9dc0bcb003d

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

[cortisiko]

🌮 🌮 🌮