4.4.1
Released
Fixes
Starting a sign-in with Google, Facebook or Apple no longer raises an error in the browser as the page leaves for the provider.
signInWithOAuthActionredirects to another origin on success, and Next settles the browser's call withundefinedbefore it navigates;OAuthProviderButtonread.statuson that and threw aTypeErrornobody caught, on every successful click. The sign-in itself was never affected — the redirect had already been issued — but each one reported an error to Sentry. The button now reads the result only when there is one, and the action's return type says it may be absent so the compiler asks for that check (#1210).
Technical changes· 1 entry for database, tooling, CI, tests and docs
Tests
oauth-buttons.test.tsxclicks a provider button with the action settling as it does on a redirect and fails on an unhandled rejection, and pins that a failed start still shows its reason (#1210).