Explanation

Temporary fix for the issue where the internal account has no scopes and or scopes is undefined
there is currently a bug where an account associated with a snap can fail to add scopes to the internal account in time
before we attempt to access this state

References

For example:

• Fixes [Sentry] TypeError: Cannot read properties of undefined (reading 'map') metamask-extension#32451
• Sentry Error
• Slack thread: https://consensys.slack.com/archives/C08T784K955/p1750172591818219

Changelog

@metamask/chain-agnostic-permission

CHANGED: isInternalAccountInPermittedAccountIds now returns false when passed an InternalAccount where scopes is undefined

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes