You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MetaMask Smart Account: when wallet connect or wallet permission sync stops in the browser consent page, the error now says where. error.details.consent_step is the page's last step: provider_choice, the wallet method whose call or answer stopped it (such as wallet_getSupportedExecutionPermissions or wallet_requestExecutionPermissions), or owner_match when a sync selects another account. When that wallet call itself threw, provider_error_code and provider_error_message carry the wallet's own code and message, unverified and reduced to printable ASCII of at most 160 characters. consent_permission_requested is true when the page had already sent MetaMask the permission request, so unless MetaMask answered with a rejection it may hold a grant. The page shows the step and code too. Before, every thrown wallet call other than a user rejection ended as "MetaMask returned an unsupported foreground consent result" with nothing more, and an error object whose properties throw left the page without any answer until the five-minute timeout. QA hit the first on a live connect on 0.5.89. Refusals and the pending intent are unchanged: retrying the same connect reuses the same session.