refactor(expo): simplify ClerkViewFactory

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mikepitre]

This follow-up PR refactors packages/expo/ios/ClerkViewFactory.swift on top of chris/mobile-460-add-two-way-jsnative-session-sync-for-expo-components without changing the intended JS/native session-sync behavior.

The underlying issue with the current Swift file is not a functional bug in the sync flow itself, but that the implementation had grown hard to read and review. ClerkViewFactory was mixing three concerns in one place: native token synchronization, raw Keychain reads and writes, and React Native bridge payload construction. That made the file harder to reason about during review and made future changes riskier, especially because the same SecItem* code paths and auth mode mapping logic were repeated in multiple places.

The effect on maintainers is review friction rather than direct user-facing breakage. The session-sync changes in the parent branch are subtle, and the surrounding Swift glue code is the main integration point between Expo and clerk-ios. Keeping that layer compact and explicit should make it easier to validate behavior changes and lower the chance of accidental regressions when the sync logic evolves.

This PR simplifies the file in a few focused ways. It introduces a small local ExpoKeychain helper so the raw Keychain plumbing is centralized rather than hand-written in several helper methods. It extracts the configure() flow into smaller pieces for token synchronization, refresh decisions, option creation, and load waiting. It also removes repeated auth-mode mapping and repeated UIHostingController setup, and it extracts session/user bridge serialization into dedicated helpers so getSession() stays short and obvious.

There should be no intended runtime behavior changes beyond the structural cleanup. The goal is to preserve the current sync semantics while making the file easier to review and safer to extend.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Mar 11, 2026 9:46pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f12714

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR