<AuthView /> component
The <AuthView /> component renders a complete native authentication interface using SwiftUI on iOS and Jetpack Compose on Android. It handles all authentication flows including email, phone, OAuth, passkeys, and multi-factor authentication. All methods enabled in your Clerk Dashboard are automatically supported.
Usage
The following examples show how to use the <AuthView /> in your Expo app. Use useAuth() or useUser() in a useEffect to react to authentication state changes.
Basic usage
import { AuthView } from '@clerk/expo/native'
import { useAuth } from '@clerk/expo'
import { useRouter } from 'expo-router'
import { useEffect } from 'react'
export default function SignInScreen() {
const { isSignedIn } = useAuth()
const router = useRouter()
useEffect(() => {
if (isSignedIn) {
router.replace('/(home)')
}
}, [isSignedIn])
return <AuthView mode="signInOrUp" />
}<AuthView mode="signIn" /><AuthView mode="signUp" />- Name
mode- Type
'signIn' | 'signUp' | 'signInOrUp'- Description
The authentication mode that determines which flows are available to the user. Defaults to
'signInOrUp'.'signIn'- Restricts the interface to sign-in flows only. Users can only authenticate with existing accounts.'signUp'- Restricts the interface to sign-up flows only. Users can only create new accounts.'signInOrUp'- Automatically determines whether to sign users in or sign them up based on whether they already have an account. This is the default mode that provides seamless authentication without requiring users to choose between sign-in and sign-up.
- Name
isDismissable- Type
boolean- Description
Whether the authentication view can be dismissed by the user. When
true, a dismiss button appears. Whenfalse, no dismiss button is shown. Defaults tofalse.
Social connection (OAuth) configuration
<AuthView /> automatically renders sign-in buttons for social connections (Google, Apple, etc.) that are enabled in your Clerk Dashboard. However, these buttons require native application credentials to be configured — without them, users will see the buttons but get an error when they tap them.
- Google: You must create OAuth credentials in Google Cloud Console and register your native applications in the Clerk Dashboard. See the Sign in with Google guide for setup steps. You do not need the
useSignInWithGoogle()hook orexpo-crypto—<AuthView />handles the flow automatically. - Apple: You must register your iOS native application (Team ID + Bundle ID) in the Clerk Dashboard. See the Sign in with Apple guide for setup steps. You do not need
expo-apple-authentication,expo-crypto, or theuseSignInWithApple()hook.
Platform support
Feedback
Last updated on