React Native SDK
@authon/react-native — Hooks, social buttons, secure token storage, and low-level OAuth helpers for React Native and Expo.
Install
Use `expo-secure-store` for token persistence. `expo-web-browser` is required for the recommended OAuth flow.
npm install @authon/react-native react-native-svg
npx expo install expo-secure-store expo-web-browserProvider Setup
import { AuthonProvider } from "@authon/react-native";
import * as SecureStore from "expo-secure-store";
const storage = {
getItem: (key: string) => SecureStore.getItemAsync(key),
setItem: (key: string, value: string) => SecureStore.setItemAsync(key, value),
removeItem: (key: string) => SecureStore.deleteItemAsync(key),
};
export default function App() {
return (
<AuthonProvider publishableKey="pk_live_..." storage={storage}>
<Navigation />
</AuthonProvider>
);
}Email / Password
import { useState } from "react";
import { View, TextInput, Button, Text, ActivityIndicator } from "react-native";
import { useAuthon, useUser } from "@authon/react-native";
export function LoginScreen() {
const { isLoaded } = useUser();
const { signIn, signOut, user, isSignedIn } = useAuthon();
const [email, setEmail] = useState("");
const [password, setPassword] = useState("");
const [loading, setLoading] = useState(false);
const [error, setError] = useState<string | null>(null);
const handleSignIn = async () => {
setLoading(true);
setError(null);
try {
await signIn({ strategy: "email_password", email, password });
} catch (err: any) {
setError(err.message ?? "Sign-in failed");
} finally {
setLoading(false);
}
};
if (!isLoaded) return <ActivityIndicator />;
if (isSignedIn) {
return (
<View style={{ padding: 24, gap: 12 }}>
<Text>Welcome, {user?.displayName ?? user?.email}</Text>
<Button title="Sign out" onPress={signOut} />
</View>
);
}
return (
<View style={{ padding: 24, gap: 12 }}>
<TextInput placeholder="Email" value={email} onChangeText={setEmail} autoCapitalize="none" />
<TextInput placeholder="Password" value={password} onChangeText={setPassword} secureTextEntry />
{error ? <Text style={{ color: "red" }}>{error}</Text> : null}
<Button title={loading ? "Signing in..." : "Sign in"} onPress={handleSignIn} disabled={loading} />
</View>
);
}Social Buttons
import { SocialButtons } from "@authon/react-native";
export function SocialLoginSection() {
return (
<SocialButtons
onSuccess={() => console.log("Signed in")}
onError={(error) => console.error(error)}
/>
);
}Recommended Expo OAuth Flow
The recommended flow uses PKCE. `startOAuth` generates the verifier and builds the provider URL, `expo-web-browser` opens the session, and `completeOAuth(result.url)` exchanges the returned `authon_code` using the verifier. `returnTo` is required and may be an HTTPS bridge page or your app deep link. The entire chain should be HTTP 3xx redirects — avoid relying on JS-based redirects in the bridge page, as Android Custom Tabs may not execute them reliably.
import * as WebBrowser from "expo-web-browser";
import { Alert, Button } from "react-native";
import { useAuthon } from "@authon/react-native";
const APP_DEEP_LINK = "myapp:0
1
2
const RETURN_TO = "https://yourapp.com/authon/mobile-callback";
export function GoogleButton() {
const { startOAuth, completeOAuth } = useAuthon();
const handlePress = async () => {
try {
// startOAuth generates the PKCE verifier (kept in the client) and
// sends only its hash. returnTo is required.
const { url } = await startOAuth("google", { returnTo: RETURN_TO });
// Returns when the browser is dismissed or the deep link is opened.
const result = await WebBrowser.openAuthSessionAsync(url, APP_DEEP_LINK);
if (result.type === "success") {
// Exchanges authon_code with the verifier and stores the tokens.
await completeOAuth(result.url);
}
} catch (err: any) {
// Do NOT silently swallow — show error and reset UI state.
Alert.alert("Login failed", err.message ?? "OAuth error");
}
};
return <Button title="Continue with Google" onPress={handlePress} />;
}HTTPS Bridge Page
The bridge page receives `authon_code` and `authon_oauth_state` from the Authon redirect and forwards the full query to your app's deep link. Prefer server-side HTTP 302 redirects over JS `window.location.replace` — this is the single most important factor for reliable browser auto-dismiss on both iOS and Android.
<!-- Recommended: HTTP redirect (server-side) -->
<!-- Your server at /authon/mobile-callback should do: -->
<!-- 302 redirect to: myapp://oauth-callback?authon_code=xxx&authon_oauth_state=yyy -->
<!-- Forward the full query string as-is, including authon_code. -->
<!-- This is more reliable than JS-based redirect on Android Custom Tabs. -->
<!-- If you cannot do server-side redirect, use this HTML fallback: -->
<!doctype html>
<html>
<body>
<script>
const params = new URLSearchParams(window.location.search);
// Forward every query parameter (authon_code, authon_oauth_state,
// authon_oauth_error, ...) to the app deep link.
const target = new URL("myapp://oauth-callback");
params.forEach((value, key) => target.searchParams.set(key, value));
// Fallback: JS redirect. Less reliable on Android Custom Tabs.
window.location.replace(target.toString());
</script>
</body>
</html>Sign Out (Important)
When signing out, always call `signOut()` which clears both local tokens AND the Authon server session. This is critical when users switch between multiple OAuth providers (e.g. Google → Kakao). Failing to clear the Authon session causes stale session interference on the next login attempt.
import { useAuthon } from "@authon/react-native";
function LogoutButton() {
const { signOut } = useAuthon();
const handleLogout = async () => {
// signOut() calls DELETE /v1/auth/signout on Authon,
// clearing the Authon session + local tokens.
// This is critical when switching between providers
// (e.g. Google → Kakao) to avoid stale session conflicts.
await signOut();
// If your app has its own backend session, clear it too:
// await myBackend.post("/api/logout");
};
return <Button title="Sign out" onPress={handleLogout} />;
}Account Deletion
Authon provides `DELETE /v1/auth/me` for users to delete their own account. The SDK exposes this as `deleteAccount()`. This is required for Apple App Store and Google Play compliance.
import { useAuthon } from "@authon/react-native";
import { Alert } from "react-native";
function DeleteAccountButton() {
const { deleteAccount, signOut } = useAuthon();
const handleDelete = () => {
Alert.alert(
"Delete Account",
"This will permanently delete your account and all data. This cannot be undone.",
[
{ text: "Cancel", style: "cancel" },
{
text: "Delete",
style: "destructive",
onPress: async () => {
try {
await deleteAccount();
// User is now signed out and account is deleted.
} catch (err: any) {
Alert.alert("Error", err.message ?? "Failed to delete account");
}
},
},
],
);
};
return <Button title="Delete Account" onPress={handleDelete} color="red" />;
}- Provider redirect URIs must always be `{apiUrl}/v1/auth/oauth/redirect`. Never point providers directly at `myapp://...` custom schemes.
- When `returnTo` is an HTTPS URL, its origin must be in the project's allowed origins. This is your bridge page that forwards to the app deep link.
- Use HTTP 3xx server redirect in your bridge page, not JS redirect. Android Custom Tabs may not reliably execute JS on intermediate pages, causing the browser to stay open.
- The redirect chain should be: Provider → api.authon.dev → your HTTPS bridge (302) → myapp://oauth-callback. All transitions should be HTTP redirects, not JS navigation.
- OAuth uses PKCE. `startOAuth` keeps the verifier in the client and `completeOAuth(callbackUrl)` exchanges `authon_code` with it. `GET /v1/auth/oauth/poll` now returns status only, so calling `completeOAuth(state)` alone can no longer get tokens.
- The origin of `returnTo`, or a custom scheme such as `myapp://`, must be registered in the project's allowed origins. `returnTo` (or `oauthReturnTo` on `AuthonProvider`) is required.
- The bridge page must forward the full query, including `authon_code`, to the app deep link. Dropping it makes the code exchange fail. Wrap `completeOAuth()` in try/catch and show the error.
- Always call `signOut()` on logout — clearing only your app's local state without revoking the Authon session causes problems when switching providers.
- For apps with their own backend session, exchange `getToken()` with your backend immediately after `completeOAuth(result.url)` resolves.
- The bridge/callback route should be locale-independent (e.g. `/authon/mobile-callback`, not `/en/authon/mobile-callback`) to avoid locale routing issues.