Description

When the user taps "Add" on the Predict balance row in the pay-with picker during a predictDepositAndOrder confirmation, the existing flow creates a predictDeposit transaction on top of the active predictDepositAndOrder confirmation. This causes two issues:

1. Stacking confirmations is unsafe - we assume a single active transaction at a time
2. The pay-with modal doesn't work on the second confirmation because it's on the wrong navigation stack

Fix

Mirror the Perps pattern (usePerpsBalanceTokenFilter):

1. dismissActivePreviewSheet() - instantly removes the PredictPreviewSheet overlay (module-level function that calls setBuyParams(null) on the active provider)
2. onReject() - rejects the existing predictDepositAndOrder approval
3. navigation.navigate(ADD_FUNDS_SHEET) - opens the deposit flow cleanly

Changes

• usePredictBalanceTokenFilter.ts - handleAddFunds now calls dismissActivePreviewSheet() + onReject() before navigating to Add Funds
• PredictPreviewSheetContext.tsx - Extended SheetModeProviderEntry with dismissPreviewSheet callback; added exported dismissActivePreviewSheet() function that dismisses the active provider's sheet from anywhere (including outside the context tree)
• contexts/index.ts - Export dismissActivePreviewSheet
• usePredictBalanceTokenFilter.test.ts - Updated test to mock useApprovalRequest, usePredictDeposit, and assert onReject is called

Manual testing steps

1. Open a prediction market and tap a bet outcome
2. In the buy sheet, tap "Pay with" to open the token picker
3. Tap "Add" next to "Predict balance"
4. Verify: the buy sheet and predictDepositAndOrder confirmation are dismissed
5. Verify: the Add Prediction Funds flow opens cleanly on top

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs
• 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
• I've properly set the title of this PR
• If applicable, I've included the Run Smoke E2E and/or Run Full E2E label to run smoke/full E2E tests