From d93e4503f44b9fc4272d47849d49afa131275f84 Mon Sep 17 00:00:00 2001
From: Nick Nisi <nick.nisi@workos.com>
Date: Fri, 15 May 2026 13:28:05 -0500
Subject: [PATCH] fix: handle createClient rejection so isLoading resolves

Without a .catch() on the createClient promise chain, any rejection
(network failure, DNS error, hung custom domain) leaves isLoading
stuck at true forever, rendering apps unable to show their
unauthenticated state.
---
 src/provider.tsx | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/provider.tsx b/src/provider.tsx
index 1f61575..24155fe 100644
--- a/src/provider.tsx
+++ b/src/provider.tsx
@@ -93,6 +93,9 @@ export function AuthKitProvider(props: AuthKitProviderProps) {
             getSignUpUrl: client.getSignUpUrl.bind(client),
           });
           setState((prev) => ({ ...prev, isLoading: false, user }));
+        })
+        .catch(() => {
+          setState((prev) => ({ ...prev, isLoading: false }));
         });
       });