Proof

expo-web-browser

the published package runs unchanged; host-owned browser sessions settle on user cancellation or programmatic dismissal, and auth sessions deliver successful callback URLs, explicit user cancellation, programmatic dismissal, and replacement. the 80% implementation estimate follows the mounted published-package test under cross-origin isolation and popup blocking; native browser presentation and unrestricted redirect schemes remain unsupported.

80%

API coverage

No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working

openBrowserAsync pending result, user cancel and programmatic dismiss, locked result for a second browser, warmUpAsync, coolDownAsync, mayInitWithUrlAsync, published iOS getCustomTabsSupportingBrowsersAsync UnavailabilityError, openAuthSessionAsync success with callback URL, explicit host Cancel Sign-In, dismissAuthSession and replacement dismissal, identity-matched callback and control cleanup, preservation of guest alerts during sign-in, and upstream enums and option processing

Missing

embedded SFSafariViewController or Chrome Custom Tab, native styling and cookie isolation, custom-scheme or foreign-origin auth callbacks, and observing abandonment after browser isolation severs the popup proxy. auth requires a same-origin HTTP(S) callback and user activation allowed by popup policy; an abandoned isolated provider requires the visible host close control