test(expo): explore aligned Kotlin dependencies on SDK 58

[eliotgevers]

Description

This draft makes an Expo 58 Android alignment experiment reproducible without changing Clerk's shipped defaults. It explores whether newer Expo consumers can use the native components without stdlib exclusions, an annotation exception, or Kotlin metadata-check bypasses.

The standalone fixture pins published @clerk/expo@4.7.1, Expo 58.0.0-preview.8 and Kotlin 2.4.20. A fixture-local pnpm patch removes the six stdlib exclusions and all three metadata-bypass paths, and supplies SavedState Compose 1.3.3. Release minification and resource shrinking stay enabled. The README provides reproduction steps, the selected-version comparison and the limits of the evidence; no production configuration or supported-version declaration changes.

I also verified a fresh pnpm install and optimized build of this publication fixture, with mapping output and no annotation suppression or metadata bypasses. Expo CLI failed only at its subsequent development-client URI launch; build and installation succeeded.

In the original isolated experiment, I verified native sign-in, token retrieval, cold restart, profile/remount and sign-out on an API 36 arm64 emulator. Dependency reports resolved both Kotlin and Compose compilers to 2.4.20 without an additional Compose patch. Physical devices, social authentication and existing-install session migration remain unverified, and older Expo compilers have separate compatibility constraints.

This complements #9791's immediate compatibility fix and #9955's optional native package split. I opened #9974 separately to enable optimization in the existing Android integration workflow. The question for this draft is whether an aligned configuration can become a supported path for newer Expo versions while retaining an appropriate publication/dependency baseline for older consumers. It is an exploratory reproduction, not a replacement fix for all supported versions.

Checklist

• pnpm test runs as expected. Full monorepo suite not run.
• pnpm build runs as expected. Full monorepo build not run.
• (If applicable) JSDoc comments have been added or updated for any package exports. Not applicable; no exports change.
• (If applicable) Documentation has been updated. Fixture README included.

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other: isolated compatibility experiment

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

_{Comment @coderabbitai help to get the list of available commands.}

[vercel]

@eliotgevers is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5cbd2e6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

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

Not sure what this means? Click here to learn what changesets are.

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