Repository navigation
docs(expo): say the test app restores the client from the native device token - #10427
Conversation
…ce token in the token-cache page Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LBNaV4iPRitNhY299sCP5X
🦋 Changeset detectedLatest commit: 2404fb0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen 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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review.
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Description
Corrects drift in the
verify-clerk-expofeature map, found by a scheduled upkeep pass that read each Expo feature against the source and drove every feature live on a remote iOS simulator (iPhone 17 Pro on macos-26).@clerk/expo's token cache restored the client from secure storage, and that theToken cachescreen shows what the JS cache itself held. The test app links@clerk/expo-native-components, soClerkProviderwraps the token cache increateNativeClientSync. clerk-js reads the client token fromnative.getDeviceToken(), and the secure-storage item is only a seed forconfigureNativeand a mirror written after each save (packages/expo/src/provider/nativeClientSync.ts). The page now says that, and the gotcha says theToken cachescreen shows whether the secure-storage copy held the token at launch.Live coverage on iOS:
r20261026-151422-1de2(run --all --no-video): 17 of 20 tests passed. Onenative-js-synctest failed when a screen read timed out in agent-device, the next test failed withinitializing engine mobile timed out, and the Google sign-in test then found no button.r20261026-153236-961creran those afterdoctor: bothnative-js-synctests that failed and the Google test passed. In the same run, two tests that had passed earlier failed. In one, iOS'sSave Password?sheet covered the home just as the spec read the session ID. In the other, the home showed the signed-in user but no UserButton.r20261026-153852-e197, at this branch's commit, rantoken-cache-persistenceand passed.Only the feature-map page and an empty changeset change.
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Generated by Claude Code
Verified on an iOS simulator, as reported by the session that
mikepitrestarted. Runr20261026-153852-e197oniPhone 17 Pro on macos-26at2404fb0589d5, 1 of 1 passed.token-cachenew-scope