Why AI tools produce this: AI coding tools generate this anti-pattern by default, it appears in a large share of AI-written auth code.
Why this matters
Embedded WebViews are an anti-pattern for OAuth: the host app can read the user's credentials and the session cookie, there is no shared SSO session with the system browser, and providers such as Google reject WebView auth outright (CWE-522). AI samples reach for a WebView because it is the simplest way to "show the login page".
Use an external user-agent instead: Chrome Custom Tabs (CustomTabsIntent) or, for full OAuth/PKCE, AppAuth's AuthorizationService.performAuthorizationRequest(...), which hands the flow to the system browser and returns via a redirect URI.
If a finding is a genuine false positive, scope the suppression to the exact line and leave a reason, never disable the rule project-wide. Disable directives are line-scoped by design.