@ikonai/sdk-react-ui 1.3.2 → 1.3.4

package/auth/oauth-continuation.d.ts

@@ -26,11 +26,19 @@ export declare function hasPendingOAuthContinuation(): boolean;
 /**
  * Report the completed sign-in and hand the browser to the consent screen.
  *
+ * The token is passed in rather than read from storage. A signed-in browser does not necessarily have
+ * one there: a session backed by a refresh cookie is held in memory and its localStorage record is
+ * deliberately REMOVED, so reading storage returned null for a fully signed-in user and the handoff
+ * waited for a session that was never going to appear. The auth context holds the live token either
+ * way, so it is the only source that is right for both.
+ *
  * Only ever called after a REAL sign-in — `useAuthGuard` treats an anonymous session as not satisfying a
  * prompt, which is the guest/global exclusion this flow needs and already had. A `global` visitor is one
  * shared space-wide user, so authorizing as one would hand every client the same identity.
  *
- * Failure clears the pointer and returns false: the app then carries on as a normally signed-in session
- * rather than trapping the user in a flow that cannot finish.
+ * Returns whether the browser was handed on to consent. Failure is not one outcome but two, and they
+ * are treated differently: something a retry could fix (no readable session yet, a failed request)
+ * keeps the pointer so a later attempt can succeed, while a refusal from the server clears it, because
+ * retrying a spent or expired authorization only traps the user in a flow that cannot finish.
  */
-export declare function completeOAuthContinuation(): Promise<boolean>;
+export declare function completeOAuthContinuation(token: string | null): Promise<boolean>;