docs(expo): update useSSO reference for core-3 and redirect URL requirements

[chriscanin]

Summary

Updates the useSSO() hook reference to reflect the core-3 migration in clerk/javascript#8140:

• Updated return type (simplified — no more setActive, signIn, signUp)
• Added authSessionOptions parameter documentation
• Added redirect URL configuration section (required for SSO to work)
• Added basic usage example showing the simplified API
• Added guidance for both dev builds and Expo Go redirect URLs

Related

• fix(expo): migrate useSSO to core-3 and fix browser dismissal for OAuth/SSO flows javascript#8140

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Mar 26, 2026 6:05pm

[chriscanin]

This docs PR relies on a JS change, status has been set to do not merge so that merge can be completed once JS has been merged in:
clerk/javascript#8140

[alexisintech]

I think we can remove this callout and instead put the link in the description of the redirectUrl prop, see the comment there!

[SarahSoutoul]

Agreed!

[alexisintech]

Suggested change

	Then register `myapp://sso-callback` in the Dashboard. This works in both Expo Go and development builds.
	Then register `myapp://sso-callback` in the Clerk Dashboard. This works in both Expo Go and development builds.

[alexisintech]

here's a quick high level review after reading through it once.

that last section may need some reworking! we can hop on a call so you can explain it to me a little more - and we can loop @SarahSoutoul in as well so she can hear about it too! and we can all work on it together :)

[chriscanin]

Thank you for the review @alexisintech , I will get this updated today and then maybe @SarahSoutoul can give it a readthrough as well for a final check.

[SarahSoutoul]

@chriscanin @alexisintech For this last section, here are my thoughts:

• The section is technically correct, but the current structure is a bit confusing because it presents "development builds" and "Expo Go" as separate setups, when in practice we want users to follow a single consistent approach. Specifically, because the Expo Go solution actually works in both environment and seems to be the most reliable approach.
• My suggested improvement is to restructure this section around one recommended setup (custom scheme + explicit redirectUrl). Sth like: here is the recommended setup and works everywhere (the primary path essentially) and then you can explain why this is needed especially for Expo Go (dynamic exp://)

I'm not sure if this is what you were referring to @alexisintech when you talked about restructuring this, but if we agree with this approach, I've got the changes locally that I could push as docs review.

[SarahSoutoul]

This is what I'm thinking

[alexisintech]

yeah that looks awesome!

[SarahSoutoul]

Okay great. @chriscanin how do you feel about this layout?

[SarahSoutoul]

Pushed here: docs review.

[chriscanin]

Layout looks good here!

[SarahSoutoul]

here's a quick high level review after reading through it once.

that last section may need some reworking! we can hop on a call so you can explain it to me a little more - and we can loop @SarahSoutoul in as well so she can hear about it too! and we can all work on it together :)

See comment here on reworking last section.

[alexisintech]

looking at fix(expo): migrate useSSO to core-3 and fix browser dismissal for OAuth/SSO flows

1. the description says that users no longer need to call setActive()
2. also the "After (app code)" example removes the redirectUrl usage too - is that to show that it will automatically set the redirectUrl to redirect to the sso-callback route?

[chriscanin]

1. Correct. The hook now calls clerk.setActive() internally after the OAuth callback completes. The caller just awaits startSSOFlow() and the session is active when it resolves.

2. Yes. If redirectUrl is not passed, the hook generates one automatically via AuthSession.makeRedirectUri({ path: 'sso-callback' }). The user can still pass a custom redirectUrl if they need to override it (e.g. to use a specific scheme for dev builds). The "After" example omits it to show the minimal usage.

[alexisintech]

@chriscanin I've updated the existing examples to follow these new requirements, and updated the redirect URL configuration section to fully clarify why certain steps need to be done

[chriscanin]

Looking good @alexisintech

for the response to the comment you had left:

Yes, the stable redirect URL using the scheme would be myapp://sso-callback (where myapp is whatever the user has set as their scheme in app.json). That's what they'd register in the Clerk Dashboard under Redirect URLs.

This works in both Expo Go and dev builds because ASWebAuthenticationSession intercepts the custom scheme regardless of whether it's registered in Info.plist.