fix(expo): preserve token cache method context by mikepitre · Pull Request #8713 · clerk/javascript

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

mikepitre · 2026-06-01T15:03:18Z

Summary

Preserve tokenCache method context when @clerk/expo wires the native Clerk singleton into clerk-js request hooks.
Add regression coverage for a class-instance token cache whose methods rely on this.
Add a patch changeset for @clerk/expo.
Plain Ticket

This was an issue with some updates internally in the clerk sdk, with how it uses the tokenCache. The previous recommended code for the tokenCache no longer worked as clerk destructured the getValue and setValue functions from the tokenCache internally. This broke the cache when implemented as a class instance and not a pure object as the functions are not bound to the class instance when they rely on instance properties from the tokenCache class.

It's worth noting that anyone using a standard setup with the recomended code from (older) clerk documentation prior to clerk exporting a tokenCache from ckerk itself will have a high chance to hit this issue, so I suggest changing the clerk react-native sdk to be backwards compatible with the older tokenCache class instance.

Customer Context

A customer upgrading to Expo 56 and the latest @clerk/expo reported that the app stayed stuck loading forever on <ClerkLoaded>, and calls such as useAuth().getToken() did not resolve on iOS Simulator 26.3.

They later narrowed it down to their older documented tokenCache implementation. Their cache was implemented as a class instance, and the cache methods depended on instance properties. Because @clerk/expo detached getToken and saveToken from the provided tokenCache, those methods lost their receiver and no longer had access to this.

This keeps both cache styles working.

Supported Token Cache Styles

Plain object cache:

consttokenCache={asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(key);},asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(key,token);},};<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Class instance cache:

classTokenCache{privateprefix='clerk:';asyncgetToken(key: string){returnawaitSecureStore.getItemAsync(this.prefix+key);}asyncsaveToken(key: string,token: string){awaitSecureStore.setItemAsync(this.prefix+key,token);}}consttokenCache=newTokenCache();<ClerkProviderpublishableKey={publishableKey}tokenCache={tokenCache}>{children}</ClerkProvider>;

Testing

pnpm --dir packages/expo exec vitest run src/provider/singleton/__tests__/createClerkInstance.test.ts
pnpm --dir packages/expo exec prettier --check src/provider/singleton/createClerkInstance.ts src/provider/singleton/__tests__/createClerkInstance.test.ts ../../.changeset/clean-token-cache.md
git diff --check

Note: pnpm --filter @clerk/expo test -- createClerkInstance ran the new singleton test successfully, but the package-level pattern also collected unrelated hook tests that require built @clerk/react exports in this fresh worktree.

vercel · 2026-06-01T15:03:25Z

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

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 1, 2026 3:03pm

pkg-pr-new · 2026-06-01T15:05:42Z

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8713

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8713

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8713

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8713

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8713

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8713

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8713

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8713

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8713

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8713

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8713

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8713

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8713

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8713

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8713

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8713

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8713

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8713

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8713

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8713

commit: 377a0a6

coderabbitai · 2026-06-01T15:16:50Z

📝 Walkthrough

Walkthrough

This PR fixes a bug where class-based token cache methods lose their this context when stored by reference during Clerk singleton initialization. The implementation wraps tokenCache.getToken and tokenCache.saveToken in arrow functions that forward calls with explicit arguments, preserving the instance context. A regression test validates the fix by using a class-based token cache instance and verifying tokens are correctly cached and retrieved through the request hooks. The changeset documents the patch release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(expo): preserve token cache method context' accurately summarizes the main change: fixing a bug where token cache methods lose their 'this' context during integration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The description thoroughly explains the issue, provides context from a customer bug report, details the fix approach, shows both supported token cache styles, and includes testing instructions.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

wobsoriano

Nice, thanks for fixing!

Two fixes for the TestFlight white-screen-at-launch incident: - @clerk/expo 3.3.0 -> 3.3.1: upstream fix (clerk/javascript#8713) preserves tokenCache method context when wiring the native Clerk singleton into clerk-js request hooks. The bug class presents as clerk load() failing silently -> isLoaded stuck false -> the splash never hides (no exception thrown anywhere). - expo-splash-screen plugin: the image/imageWidth lived only under the android key, so prebuild generated an iOS storyboard with NO customization at all - systemBackgroundColor (white) and no logo, which is why the stuck splash reads as a blank white screen. Moving image/imageWidth to the plugin root gives iOS the brand background (#0D8348) + logo (verified in the generated SplashScreen.storyboard: named color sRGB 0.051/0.514/0.282 + SplashScreenLogo 76px). Also picks up prebuild's scripts rewrite (expo run:ios/run:android). Verified: Release-configuration simulator build (Doppler dev env) launches to the sign-in screen; lint/typecheck/test green. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

fix(expo): preserve token cache method context
377a0a6

vercelBotdeployed to Preview June 1, 2026 15:03 View deployment

github-actionsBot added the expo label Jun 1, 2026

mikepitre marked this pull request as ready for review June 1, 2026 15:14

mikepitre requested review from brkalow, octoper and wobsoriano June 1, 2026 15:15

wobsoriano approved these changes Jun 1, 2026
View reviewed changes

jacekradko merged commit e2b6a9f into mainJun 1, 2026
78 checks passed

jacekradko deleted the mike/expo-token-cache-issue branch June 1, 2026 17:54

clerk-cookie mentioned this pull request Jun 1, 2026
ci(repo): Version packages #8679
Merged

honerlaw mentioned this pull request Jun 6, 2026
fix: bump @clerk/expo to 3.3.1 and give iOS a real splash screen honerlaw/vital#23
Merged

coderabbitaiBot mentioned this pull request Jun 27, 2026
Implemented login and logout functionality kkrissshnaa/Recurly#5
Merged