@oxyhq/services 22.13.0 → 23.0.0

package/src/notifications/deviceNotifications.ts

@@ -0,0 +1,458 @@
+/**
+ * The ONE place `@oxyhq/services` touches `expo-notifications`.
+ *
+ * Every Oxy app that receives push needs the identical adapter — native-only,
+ * dynamically imported, reading the OS permission and minting an EXPO push
+ * token — so it lives here instead of being copied into each app. The
+ * bearer-authenticated transport (`registerPushToken` / `unregisterPushToken`)
+ * already lives in `@oxyhq/core`; core may never import an `expo-*` module, and
+ * this adapter is the Expo-side half that closes that gap.
+ *
+ * ## Native-only by construction
+ *
+ * Every entry point resolves its null/no-op result from `Platform.OS` BEFORE the
+ * dynamic `import()`, so a web bundle never requests `expo-notifications` at all.
+ * `expo-notifications` and `expo-constants` are OPTIONAL peer dependencies: an
+ * app that does not use push never installs them, and a build without them
+ * degrades to "notifications unavailable" rather than throwing at
+ * module-evaluation time.
+ *
+ * ## The token is an EXPO push token — never a raw device token
+ *
+ * {@link getExpoPushToken} calls `getExpoPushTokenAsync()`, which returns the
+ * `ExponentPushToken[…]` handle Expo's push service delivers through — the only
+ * form it accepts. `getDevicePushTokenAsync()` — the raw APNs/FCM token — is
+ * deliberately NOT used anywhere: registering one of those looks entirely
+ * successful (the row is stored, the endpoint returns 200) and then every push
+ * silently fails at delivery time. `@oxyhq/core`'s `registerPushToken` rejects a
+ * raw device token before sending, and this module is the reason it never has to.
+ *
+ * ## The payload is untrusted
+ *
+ * Nothing here surfaces a notification's `title` / `body` / `subtitle`. The only
+ * payload that leaves this module is the raw `content.data` — the routing keys —
+ * typed `unknown`, so a caller has to validate it before acting on it and there
+ * is no exported shape that invites rendering push-delivered text. The
+ * foreground handler likewise answers with a visibility verdict and nothing else.
+ */
+
+import { createLogger } from '@oxyhq/core';
+import type { PushTokenPlatform } from '@oxyhq/core';
+import { Platform } from 'react-native';
+
+const log = createLogger('deviceNotifications');
+
+type NotificationsModule = typeof import('expo-notifications');
+type ConstantsModule = typeof import('expo-constants');
+
+function isRecord(value: unknown): value is Record<string, unknown> {
+  return typeof value === 'object' && value !== null;
+}
+
+/**
+ * Load `expo-notifications`, or `null` when it cannot serve this platform/build.
+ *
+ * The web guard runs before the `import()`, so a web bundle never reaches for the
+ * native module. The dynamic import is intentional: the module registry caches
+ * it, so repeated calls are cheap and no module-level mutable cache is
+ * introduced here.
+ */
+async function loadNotifications(): Promise<NotificationsModule | null> {
+  if (Platform.OS === 'web') {
+    return null;
+  }
+  try {
+    return await import('expo-notifications');
+  } catch (error) {
+    log.warn(
+      'expo-notifications is unavailable in this build — push is disabled',
+      { method: 'loadNotifications' },
+      error,
+    );
+    return null;
+  }
+}
+
+/**
+ * The EAS project id an Expo push token is minted against, or `null` when the
+ * app config carries none.
+ *
+ * Resolved exactly the way `expo-notifications` resolves it internally
+ * (`easConfig.projectId`, then `expoConfig.extra.eas.projectId`) and then handed
+ * BACK to `getExpoPushTokenAsync` explicitly, so the two can never disagree.
+ * Reading it here is what turns "no project id" from an opaque
+ * `ERR_NOTIFICATIONS_NO_EXPERIENCE_ID` rejection into a named, actionable state
+ * instead of one more entry in the indistinguishable "permission denied /
+ * offline" bucket.
+ *
+ * A missing `expo-constants` lands on the same `null` outcome — the single
+ * actionable warning is emitted once by the caller, so this path only records
+ * the extra detail at debug level rather than warning twice for one condition.
+ */
+async function easProjectId(): Promise<string | null> {
+  let constants: ConstantsModule['default'];
+  try {
+    constants = (await import('expo-constants')).default;
+  } catch (error) {
+    log.debug(
+      'expo-constants is unavailable in this build — no EAS project id can be resolved',
+      { method: 'easProjectId' },
+      error,
+    );
+    return null;
+  }
+
+  const fromEasConfig = constants.easConfig?.projectId;
+  if (typeof fromEasConfig === 'string' && fromEasConfig.length > 0) {
+    return fromEasConfig;
+  }
+
+  const extra: unknown = constants.expoConfig?.extra;
+  const eas = isRecord(extra) ? extra.eas : undefined;
+  const projectId = isRecord(eas) ? eas.projectId : undefined;
+  return typeof projectId === 'string' && projectId.length > 0 ? projectId : null;
+}
+
+/**
+ * The platform tag the push-token registry stores this installation under, or
+ * `null` on a platform Oxy does not deliver push to.
+ *
+ * Synchronous and import-free — the answer is a property of the bundle, not of
+ * any native module.
+ *
+ * Web is `null` on purpose: the registry accepts a `web` platform, but browser
+ * push needs a VAPID key + service-worker subscription no Oxy app has wired, so
+ * there is no token to register and claiming otherwise would store a row nothing
+ * can ever deliver to.
+ */
+export function pushTokenPlatform(): PushTokenPlatform | null {
+  return Platform.OS === 'ios' || Platform.OS === 'android' ? Platform.OS : null;
+}
+
+/**
+ * Whether the OS notification permission is ALREADY granted.
+ *
+ * Never prompts, so an app can re-check on every cold boot without ever asking
+ * the user twice. Use {@link requestNotificationPermission} for the one place
+ * that is allowed to show the system dialog.
+ */
+export async function hasNotificationPermission(): Promise<boolean> {
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return false;
+  }
+  try {
+    const permissions = await notifications.getPermissionsAsync();
+    return permissions.granted === true;
+  } catch (error) {
+    log.warn(
+      'could not read the notification permission',
+      { method: 'hasNotificationPermission' },
+      error,
+    );
+    return false;
+  }
+}
+
+/**
+ * Ensure the OS notification permission, prompting at most once.
+ *
+ * An installation that already answered the system dialog is never asked again:
+ * an already-granted permission resolves `true` without a second dialog, and a
+ * denial with `canAskAgain: false` resolves `false` without issuing a request
+ * the OS would silently ignore.
+ *
+ * @returns Whether notifications are granted once this call is done.
+ */
+export async function requestNotificationPermission(): Promise<boolean> {
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return false;
+  }
+  try {
+    const existing = await notifications.getPermissionsAsync();
+    if (existing.granted === true) {
+      return true;
+    }
+    if (existing.canAskAgain === false) {
+      return false;
+    }
+    const requested = await notifications.requestPermissionsAsync();
+    return requested.granted === true;
+  } catch (error) {
+    log.warn(
+      'the notification permission could not be resolved',
+      { method: 'requestNotificationPermission' },
+      error,
+    );
+    return false;
+  }
+}
+
+/**
+ * This installation's Expo push token (`ExponentPushToken[…]`), or `null` when
+ * one cannot be minted.
+ *
+ * Deliberately `getExpoPushTokenAsync` — see the module header for why the raw
+ * device-token variant is never used.
+ *
+ * Every `null` is logged with the reason it happened. A missing EAS project id
+ * in particular is a BUILD MISCONFIGURATION, not a user state: no token can ever
+ * be minted, so push is off for every install of that build until the config is
+ * fixed. It is reported as such rather than blending into the
+ * indistinguishable "permission denied / offline" bucket.
+ */
+export async function getExpoPushToken(): Promise<string | null> {
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return null;
+  }
+
+  const projectId = await easProjectId();
+  if (!projectId) {
+    log.warn(
+      'no EAS project id in the app config (expo.extra.eas.projectId) — an Expo push token cannot be minted, so push is disabled for this build',
+      { method: 'getExpoPushToken' },
+    );
+    return null;
+  }
+
+  try {
+    const token = await notifications.getExpoPushTokenAsync({ projectId });
+    if (token.data.length === 0) {
+      log.warn('the Expo push service returned an empty token', { method: 'getExpoPushToken' });
+      return null;
+    }
+    return token.data;
+  } catch (error) {
+    log.warn('could not mint an Expo push token', { method: 'getExpoPushToken' }, error);
+    return null;
+  }
+}
+
+/**
+ * Take the payload of the notification that COLD-LAUNCHED the app, if any.
+ *
+ * "Take" is literal: the response is cleared from `expo-notifications` once
+ * read, so a listener attached later in the same launch is not handed the same
+ * tap again. Clearing is best-effort across OS/module versions, so a caller that
+ * must not act twice still needs its own idempotency ledger.
+ *
+ * @returns The raw, untrusted `content.data` of the launching notification, or
+ *   `null`. Parsing/validation is the caller's job.
+ */
+export async function takeLaunchNotificationData(): Promise<unknown> {
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return null;
+  }
+  try {
+    const response = notifications.getLastNotificationResponse();
+    if (!response) {
+      return null;
+    }
+    const data: unknown = response.notification.request.content.data;
+    try {
+      notifications.clearLastNotificationResponse();
+    } catch (clearError) {
+      log.warn(
+        'could not clear the launching notification response',
+        { method: 'takeLaunchNotificationData' },
+        clearError,
+      );
+    }
+    return data;
+  } catch (error) {
+    log.warn(
+      'could not read the launching notification',
+      { method: 'takeLaunchNotificationData' },
+      error,
+    );
+    return null;
+  }
+}
+
+/**
+ * What the OS should do with a notification that arrives while the app is
+ * FOREGROUNDED.
+ *
+ * `'suppress'` is `expo-notifications`' own default for a foregrounded app, so a
+ * decision function that only ever returns `'show'` for the payloads it
+ * recognises leaves every other notification exactly as it behaves today.
+ */
+export type ForegroundPresentation = 'show' | 'suppress';
+
+/**
+ * Whether the process-wide foreground handler has already been ATTEMPTED.
+ *
+ * `setNotificationHandler` is global, last-writer-wins process state, so this is
+ * a one-shot install rather than something a mount/unmount cycle owns. A failed
+ * attempt is deliberately not retried: the only failure modes are permanent for
+ * the life of the process (web, a build without the native module, a native
+ * module that threw on registration).
+ *
+ * Module-scoped and only ever touched from an async install call — never read
+ * during render, so the React Compiler has no memoizable position to freeze it
+ * into.
+ */
+let foregroundHandlerAttempted = false;
+
+/** How prominently Android surfaces a channel's notifications. */
+export type NotificationChannelImportance = 'default' | 'high';
+
+/** An Android notification channel this app delivers on. */
+export interface NotificationChannelSpec {
+  /**
+   * The channel id. It MUST match the id the sender attaches: Android 8+ drops
+   * a notification whose channel the app has not created, silently and with no
+   * error on either side, which is the hardest push symptom there is to
+   * diagnose. Ids that cross the wire belong in `@oxyhq/contracts`, not in a
+   * string typed on both sides.
+   */
+  id: string;
+  /** User-visible channel name — app copy, so the caller localizes it. */
+  name: string;
+  /** User-visible description shown in Android's notification settings. */
+  description?: string;
+  importance?: NotificationChannelImportance;
+}
+
+/**
+ * Create (or update) an Android notification channel.
+ *
+ * A no-op everywhere but Android: iOS has no channels, and web never loads the
+ * native module. Call it BEFORE registering a push token, so the very first
+ * notification the server sends already has a channel to land on.
+ *
+ * Failure is non-fatal and logged: a missing channel costs visibility, and
+ * refusing to register a token over it would cost the feature entirely.
+ *
+ * @returns Whether the channel was actually created (`false` off Android, or
+ *   when the native module is unavailable, or when creation failed).
+ */
+export async function ensureNotificationChannel(
+  spec: NotificationChannelSpec,
+): Promise<boolean> {
+  if (Platform.OS !== 'android') {
+    return false;
+  }
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return false;
+  }
+  try {
+    await notifications.setNotificationChannelAsync(spec.id, {
+      name: spec.name,
+      importance:
+        spec.importance === 'high'
+          ? notifications.AndroidImportance.HIGH
+          : notifications.AndroidImportance.DEFAULT,
+      ...(spec.description ? { description: spec.description } : {}),
+    });
+    return true;
+  } catch (error) {
+    log.warn(
+      'could not create the notification channel',
+      { method: 'ensureNotificationChannel', channelId: spec.id },
+      error,
+    );
+    return false;
+  }
+}
+
+/**
+ * Install the ONE process-wide handler that decides whether an incoming
+ * notification is shown while the app is in the FOREGROUND.
+ *
+ * Without a handler, `expo-notifications` shows nothing at all while the app is
+ * open — which is exactly when a time-critical notification (a "Sign in with
+ * Oxy" approval request, say) matters most, because the user is already holding
+ * the phone.
+ *
+ * The handler ONLY decides visibility. It never navigates, never acts on the
+ * notification, and never reads the payload for display — `decide` is handed the
+ * raw, untrusted `content.data` and may answer nothing but `'show'` /
+ * `'suppress'`. Acting on a notification stays with a TAP, routed by
+ * {@link subscribeToNotificationResponses}. No notification actions/categories
+ * are registered here, so the banner cannot carry an action button.
+ *
+ * The one-shot latch is set BEFORE the first `await`, so concurrent callers
+ * cannot both reach `setNotificationHandler`.
+ *
+ * @param decide - Maps the raw, untrusted payload to a presentation verdict.
+ *   Must not throw; a throw is reported by the OS as a handling error and the
+ *   notification is dropped.
+ * @returns Whether a handler was installed by THIS call (`false` on a repeat
+ *   call, on web, or when the native module is unavailable).
+ */
+export async function installForegroundNotificationHandler(
+  decide: (data: unknown) => ForegroundPresentation,
+): Promise<boolean> {
+  if (foregroundHandlerAttempted) {
+    return false;
+  }
+  foregroundHandlerAttempted = true;
+
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return false;
+  }
+  try {
+    notifications.setNotificationHandler({
+      handleNotification: async (notification) => {
+        const data: unknown = notification.request.content.data;
+        const show = decide(data) === 'show';
+        return {
+          // Banner: the whole point — make the notification visible on screen.
+          shouldShowBanner: show,
+          // Notification centre: so the user can still review it after
+          // dismissing the banner.
+          shouldShowList: show,
+          // No sound: the app is foregrounded, so the user is already looking at
+          // the screen the banner appears on.
+          shouldPlaySound: false,
+          // Badging is an app-level unread concept this adapter has no view of.
+          shouldSetBadge: false,
+        };
+      },
+    });
+    return true;
+  } catch (error) {
+    log.warn(
+      'could not install the foreground notification handler',
+      { method: 'installForegroundNotificationHandler' },
+      error,
+    );
+    return false;
+  }
+}
+
+/**
+ * Subscribe to notification TAPS (responses) while the app is running.
+ *
+ * @param listener - Receives the raw, untrusted `content.data` of the tapped
+ *   notification. Parsing/validation is the caller's job.
+ * @returns An unsubscribe function. Safe to call even if the subscription could
+ *   not be established.
+ */
+export async function subscribeToNotificationResponses(
+  listener: (data: unknown) => void,
+): Promise<() => void> {
+  const notifications = await loadNotifications();
+  if (!notifications) {
+    return () => undefined;
+  }
+  try {
+    const subscription = notifications.addNotificationResponseReceivedListener((response) => {
+      listener(response.notification.request.content.data);
+    });
+    return () => subscription.remove();
+  } catch (error) {
+    log.warn(
+      'could not subscribe to notification taps',
+      { method: 'subscribeToNotificationResponses' },
+      error,
+    );
+    return () => undefined;
+  }
+}

package/src/ui/boot/__tests__/coldBootNoIdpRedirect.test.ts

@@ -0,0 +1,215 @@
+/**
+ * `runProviderColdBoot` — the boot NEVER navigates the top-level window (#691
+ * phase 7b).
+ *
+ * Phase 7b deleted the two SDK-initiated, gesture-less full-page hops to the
+ * IdP: the cold-boot `prompt=none` silent restore and the post-sign-in hub sync.
+ * A web origin with no local device credential now resolves SIGNED OUT and waits
+ * for the user's next explicit "Continue with Oxy".
+ *
+ * What must still work — and is asserted here — is everything the user actually
+ * asked for: an authorization code ALREADY on the URL is completed, which is how
+ * a browser-BLOCKED sign-in popup finishes after `startWebOAuthSignIn` falls
+ * back to a full-page redirect.
+ *
+ * Unlike `__tests__/boot/runProviderColdBoot.test.ts` (deadline + connectivity
+ * wiring), this suite keeps the real navigation primitive in view: every
+ * assertion below reaches `redirectToAuthorize`, the ONLY top-level-window
+ * navigation the boot could ever have performed.
+ */
+
+import type { AuthStateStore, PersistedAuthState, SessionClient } from '@oxyhq/core';
+
+jest.mock('@oxyhq/core', () => {
+  const actual = jest.requireActual('@oxyhq/core');
+  return {
+    __esModule: true,
+    ...actual,
+    runSessionColdBoot: jest.fn(),
+  };
+});
+
+// The ONLY top-level-window navigation primitive the SDK has.
+jest.mock('../../components/oauthNavigation', () => ({
+  redirectToAuthorize: jest.fn(),
+}));
+
+jest.mock('../../utils/oauthReturn', () => {
+  const actual = jest.requireActual('../../utils/oauthReturn');
+  return {
+    __esModule: true,
+    ...actual,
+    tryCompleteOAuthReturn: jest.fn(async () => false),
+  };
+});
+
+import { runSessionColdBoot } from '@oxyhq/core';
+import { redirectToAuthorize } from '../../components/oauthNavigation';
+import { tryCompleteOAuthReturn } from '../../utils/oauthReturn';
+import { runProviderColdBoot, type RunProviderColdBootOptions } from '../runProviderColdBoot';
+
+const mockRunSessionColdBoot = runSessionColdBoot as jest.Mock;
+const mockRedirectToAuthorize = redirectToAuthorize as jest.Mock;
+const mockTryCompleteOAuthReturn = tryCompleteOAuthReturn as jest.Mock;
+
+const CLIENT_ID = 'oxy_dk_test';
+
+/** An auth store holding no device credential — the signed-out domain case. */
+function makeEmptyAuthStore(): AuthStateStore {
+  return {
+    load: jest.fn(async (): Promise<PersistedAuthState | null> => null),
+    save: jest.fn(async () => undefined),
+    clear: jest.fn(async () => undefined),
+  } as unknown as AuthStateStore;
+}
+
+interface Harness {
+  options: RunProviderColdBootOptions;
+  commitSession: jest.Mock;
+  markAuthResolved: jest.Mock;
+  setTokenReady: jest.Mock;
+  sessionClientStart: jest.Mock;
+}
+
+function makeHarness(overrides: Partial<RunProviderColdBootOptions> = {}): Harness {
+  const commitSession = jest.fn(async () => undefined);
+  const markAuthResolved = jest.fn();
+  const setTokenReady = jest.fn();
+  const sessionClientStart = jest.fn(async () => undefined);
+
+  const options: RunProviderColdBootOptions = {
+    oxyServices: {} as RunProviderColdBootOptions['oxyServices'],
+    authStore: makeEmptyAuthStore(),
+    clientId: CLIENT_ID,
+    sessionClient: { start: sessionClientStart } as unknown as SessionClient,
+    syncDeviceCredentialToHost: jest.fn(async () => undefined),
+    commitSession,
+    markAuthResolved,
+    setTokenReady,
+    ...overrides,
+  };
+
+  return { options, commitSession, markAuthResolved, setTokenReady, sessionClientStart };
+}
+
+/** `runSessionColdBoot` finding no session at all — the signed-out domain. */
+function stubSignedOutBoot(): void {
+  mockRunSessionColdBoot.mockImplementation(
+    async (opts: Parameters<typeof runSessionColdBoot>[0]) => {
+      await opts.onSignedOut?.('no_session');
+      return { kind: 'unauthenticated' } as const;
+    },
+  );
+}
+
+describe('runProviderColdBoot — no SDK-initiated IdP navigation (#691 phase 7b)', () => {
+  beforeEach(() => {
+    mockRunSessionColdBoot.mockReset();
+    mockRedirectToAuthorize.mockClear();
+    mockTryCompleteOAuthReturn.mockClear();
+    mockTryCompleteOAuthReturn.mockImplementation(async () => false);
+    globalThis.sessionStorage?.clear();
+  });
+
+  it('resolves a domain with no local credential SIGNED OUT instead of bouncing to the IdP', async () => {
+    stubSignedOutBoot();
+    const { options, markAuthResolved, commitSession, sessionClientStart } = makeHarness();
+
+    await runProviderColdBoot(options);
+
+    // Auth resolution concluded (routing can settle), nothing was committed,
+    // and with no persisted credential the device socket is not started.
+    expect(markAuthResolved).toHaveBeenCalled();
+    expect(commitSession).not.toHaveBeenCalled();
+    expect(sessionClientStart).not.toHaveBeenCalled();
+    expect(mockRedirectToAuthorize).not.toHaveBeenCalled();
+  });
+
+  it('does not navigate even with a clientId configured and the mint finding nothing', async () => {
+    // The deleted silent-restore lane needed exactly this shape: a registered
+    // client id plus a signed-out mint outcome. It must now be inert.
+    stubSignedOutBoot();
+    const { options } = makeHarness({ clientId: CLIENT_ID, authRedirectUri: 'https://app.oxy.so' });
+
+    await runProviderColdBoot(options);
+
+    expect(mockRedirectToAuthorize).not.toHaveBeenCalled();
+  });
+
+  it('does not navigate when the mint already resolved a session', async () => {
+    mockRunSessionColdBoot.mockImplementation(
+      async (opts: Parameters<typeof runSessionColdBoot>[0]) => {
+        const session = {
+          sessionId: 's1',
+          userId: 'u1',
+          accessToken: 'at',
+          via: 'device-secret-mint',
+        };
+        await opts.onSession?.(session);
+        return { kind: 'session', via: session.via, session } as const;
+      },
+    );
+    const { options, commitSession } = makeHarness();
+
+    await runProviderColdBoot(options);
+
+    expect(commitSession).toHaveBeenCalledWith(
+      { sessionId: 's1', accessToken: 'at', userId: 'u1' },
+      { activate: false },
+    );
+    expect(mockRedirectToAuthorize).not.toHaveBeenCalled();
+  });
+
+  describe('the blocked-popup redirect fallback still completes', () => {
+    it('completes an authorization code already on the URL', async () => {
+      // A popup-mode app lands here whenever the browser blocked the popup and
+      // `startWebOAuthSignIn` fell back to a full-page redirect.
+      mockTryCompleteOAuthReturn.mockImplementation(async () => true);
+      const { options, markAuthResolved, setTokenReady } = makeHarness();
+
+      await runProviderColdBoot(options);
+
+      expect(mockTryCompleteOAuthReturn).toHaveBeenCalledTimes(1);
+      expect(setTokenReady).toHaveBeenLastCalledWith(true);
+      expect(markAuthResolved).toHaveBeenCalled();
+      // The device mint is short-circuited by the completed return leg.
+      expect(mockRunSessionColdBoot).not.toHaveBeenCalled();
+      expect(mockRedirectToAuthorize).not.toHaveBeenCalled();
+    });
+
+    it('runs the return leg even on a boot that finds no session', async () => {
+      stubSignedOutBoot();
+      const { options } = makeHarness();
+
+      await runProviderColdBoot(options);
+
+      expect(mockTryCompleteOAuthReturn).toHaveBeenCalledTimes(1);
+    });
+
+    it('commits the OAuth return as a deliberate sign-in', async () => {
+      mockTryCompleteOAuthReturn.mockImplementation(async () => true);
+      const { options } = makeHarness();
+
+      await runProviderColdBoot(options);
+
+      const commit = mockTryCompleteOAuthReturn.mock.calls[0][0] as {
+        commitSession: (input: unknown) => Promise<void>;
+      };
+      await commit.commitSession({ sessionId: 's1', userId: 'u1' });
+      expect(options.commitSession).toHaveBeenCalledWith(
+        { sessionId: 's1', userId: 'u1' },
+        { activate: true },
+      );
+    });
+  });
+
+  it('identity mode skips the web OAuth return leg entirely', async () => {
+    stubSignedOutBoot();
+    const { options } = makeHarness({ sessionMode: 'identity' });
+
+    await runProviderColdBoot(options);
+
+    expect(mockTryCompleteOAuthReturn).not.toHaveBeenCalled();
+    expect(mockRedirectToAuthorize).not.toHaveBeenCalled();
+  });
+});