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: a permission now keeps one consent origin. MetaMask stores an Advanced Permission for the exact origin that requested it and lists it only to that origin, while APN served every consent page on a new random loopback port. So wallet permission sync asked from another origin, got an empty list, and would have recorded a live permission as revoked with revocation_freshness: confirmed_absent. MetaMask also asked to connect the page again on every run. The port of http://127.0.0.1:<port> is now saved in the permission record before its first consent and reused by every retry of the same connect and by sync. A busy port refuses with APN_PROVIDER_UNAVAILABLE (consent_port_in_use, retryable) before the browser opens; a sync that hits it records the permission's freshness as unverified, as for any sync whose consent did not run. A permission connected before 0.5.91 has no recorded origin: sync refuses it with APN_PROVIDER_EFFECT_UNAVAILABLE (consent_origin_unrecorded) and leaves it unchanged, and a pending intent from before 0.5.91 gets its port at its next connect. None of the live connects QA ran had completed, so no saved permission had been marked this way. A permission record that has a consent port cannot be read by 0.5.90 or earlier.