fix: adding alert for network RPC issue#30351
Conversation
|
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. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d2bb216. Configure here.
|
@metamaskbot update-mobile-fixture |
|
🔄 Fixture update started. Running workflow from branch |
|
❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use |
|
@metamaskbot update-mobile-fixture |
1 similar comment
|
@metamaskbot update-mobile-fixture |
|
🔄 Fixture update started. Running workflow from branch |
|
❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use |
|
@metamaskbot update-mobile-fixture |
|
🔄 Fixture update started. Running workflow from branch |
|
❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use |
|
@metamaskbot update-mobile-fixture |
|
🔄 Fixture update started. Running workflow from branch |
|
❌ E2E fixture update failed.\n\nCommon causes:\n- CI workflow is still running — wait for 'Build iOS Apps' to complete\n- CI workflow was skipped — ensure your PR has iOS-impacting changes or use |
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
Why SmokeConfirmations: The changes directly affect the send flow's amount entry step, which is part of the confirmations system. The No other tags needed: The changes are isolated to the send/amount flow within confirmations. No swap, stake, network management, or account management flows are affected. The network status check is read-only from NetworkController state and doesn't modify network configuration. Performance Test Selection: |
|
OGPoyraz
left a comment
There was a problem hiding this comment.
Approving as fix will be followup






Description
Add alert on send page if RPC url is not correct.
Changelog
CHANGELOG entry:
Related issues
Fixes: https://consensyssoftware.atlassian.net/browse/CONF-1399
Manual testing steps
Screenshots/Recordings
Screen.Recording.2026-05-19.at.10.34.44.AM.mov
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Medium Risk
Changes the send amount step to depend on NetworkController connectivity metadata, disabling progression and auto-showing a modal that can navigate to
EDIT_NETWORK. Risk is moderate because it alters user flow gating and navigation behavior during sends, but is scoped and covered by new tests.Overview
Adds an unreliable network guard to the send amount step: when
NetworkControllerreports the selected chain’s RPC as non-Available, the amount screen now disables Continue and auto-opens aSendAlertModalprompting the user to Update network settings.Introduces
useUnreliableNetworkAlert(with tests) to derive the alert from the currentchainIdand network metadata and to navigate toRoutes.EDIT_NETWORKwith the active RPC URL; addsAmountAlerts(with tests) to manage modal open/close behavior per chain. Updates English strings for the new alert title/description and “Update” label.Reviewed by Cursor Bugbot for commit 11380f2. Bugbot is set up for automated code reviews on this repo. Configure here.